Support ensure parameter with Optional data type #292
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add support for specifying the ensure parameter as an Optional Enum data type. This permits resource properties of types specified this way to be managed but only if the resource is already present and cleanly skipped otherwise. This is a behavior already present in many traditional Puppet resource types and this extends the option to the Resource API, easing transition of existing resource types to the Resource API.
|
|
michaeltlombardi
approved these changes
Jan 11, 2022
|
LGTM! Merging despite the codecov misbehaving. |
seanmil
pushed a commit
to seanmil/puppet-resource_api
that referenced
this pull request
Jan 11, 2022
Support ensure parameter with Optional data type
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add support for specifying the ensure parameter as an
Optional Enum data type.
This permits resource properties of types specified this way
to be managed but only if the resource is already present and
cleanly skipped otherwise.
This is a behavior already present in many traditional Puppet
resource types and this extends the option to the Resource API,
easing transition of existing resource types to the Resource API.