Uploaded image for project: 'Modules'
  1. Modules
  2. MODULES-7197

dsc_lite : Ensure ensurable matches actual resource more accurately

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Normal
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: dsc_lite
    • Labels:
      None
    • Template:
    • Acceptance Criteria:
      Hide

      Unit and acceptance tests are updated to cope with the new single-ensurable code, documentation in the code and readme both explain the ensurable property and discourage users from including it in their manfiests for this type.

      Ensurable is reduced to a single value which it defaults to and which calls provider.create unless provider.exists? to ensure idempotency.

      Show
      Unit and acceptance tests are updated to cope with the new single-ensurable code, documentation in the code and readme both explain the ensurable property and discourage users from including it in their manfiests for this type. Ensurable is reduced to a single value which it defaults to and which calls provider.create unless provider.exists? to ensure idempotency.
    • Epic Link:
    • Team:
      Windows
    • Story Points:
      1
    • Sprint:
      Windows 2018-06-20
    • QA Risk Assessment:
      Needs Assessment

      Description

       

      Desired Behavior:

      As a dsc_lite user
      I want to have an ensurable property which matches what the resource is actually doing and documentation to explain why this ensurable property may not look like others I am used to
      So that I can understand and utilize the dsc_lite module, and therefore PowerShell DSC modules through Puppet, with greater safety and understanding.

      Actual Behavior:

      The dsc_lite type defines ensurable with values for exists?, create, and destroy even though create and destroy call the same code path and neither of them actually verify whether the dsc resource is being created or destroyed.  A further problem is that one can theoretically set opposing ensure properties in both the property hash and in the puppet resource and only the value from the property hash will apply. This is non-intuitive.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              michael.lombardi Michael Lombardi
              Reporter:
              michael.lombardi Michael Lombardi
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support