(PDK-911) Fix handling of ensure
values from symbols to strings
#55
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.
Tripping over puppet's behaviour for handling newvalue values, rsapi
would accidentally pass symbols for
Enum[absent, present]
ensures.The unit and integration tests did not agree on whether
absent
andpresent
should be strings or symbols. Puppet itself is calling fora string as a value for
Enum
s, and in the implementation those twowere only symbols because of a special case in the setup of the two.
This commit fixes this behaviour to always use string. This makes it
consistent with the rest of the API, and reduces the amount of noise
developers have to remember when working with values passed from us.