Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(GH-105) Ensure set runs on ambiguous ensure states #108

Merged
merged 1 commit into from
Feb 12, 2021
Merged

(GH-105) Ensure set runs on ambiguous ensure states #108

merged 1 commit into from
Feb 12, 2021

Conversation

michaeltlombardi
Copy link
Contributor

Prior to this commit if a resource is ensurable but the value of ensure on the target node was not Present or Absent the call to run Invoke-DscResource never gets made.

This commit updates the logic in the set method to call update() if the state of the ensurable resource is ambiguous from a CRUD perspective, which is preferable to not running set at all.

@michaeltlombardi michaeltlombardi requested a review from a team as a code owner February 11, 2021 17:35
Prior to this commit if a resource is ensurable but the value of ensure on
the target node was not Present or Absent the call to run Invoke-DscResource
never gets made.

This commit updates the logic in the set method to call update() if the state
of the ensurable resource is ambiguous from a CRUD perspective, which is
preferable to not running set at all.
@michaeltlombardi michaeltlombardi merged commit 65b23a6 into puppetlabs:main Feb 12, 2021
@michaeltlombardi michaeltlombardi deleted the gh-105/main/call-update-on-ambiguous-ensure branch February 12, 2021 00:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants