Fix order of access.conf entries when allowed_users is a Hash #71
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.
In Ruby 1.8.7 the order of a Hash is "random" [1]. One way to ensure consistent order of elements when iterating over a Hash is to sort by the keys then reference the value using
Hash[key]
. Example of RSpec test output before changingtemplates/access.conf.erb
.I observed this issue in production when using a Hash defined in Hiera. Puppet kept changing the order of the "allow" entries in access.conf.
[1] : http://www.ruby-doc.org/core-1.8.7/Hash.html - "The order in which you traverse a hash by either key or value may seem arbitrary, and will generally not be in the insertion order."