Use Mash to handle string and symbol keys #7
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
Users may pass string instead of symbol in the permissions hashes, the resource should either fail or handle them properly. This patch propose to handle them properly using Chef Mash. Before this patch the resource was not idempotent as during the 2nd run, a diff was computed, something similar to: -'user' +:user
Annih
force-pushed
the
indifferent_acl_hash_access
branch
from
649fd30 to
996baa9
Compare
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.
Users may pass string instead of symbol in the permissions hashes, the resource should either fail or handle them properly.
This patch propose to handle them properly using Chef Mash.
Before this patch the resource was not idempotent as during the 2nd run, a diff was computed, something similar to: