fixed method for sorting hashes in gitlab.rb to sort ldap hashes too #116
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
|
Ironic. I'm been having exactly this problem, and didn't realize why until I just wandered by to see what PR's were up for this module. I'm going to give this a try ASAP. |
|
I had to resolve some merge conflicts, hopefully I did it in the correct way... |
|
cool thanks a lot! |
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.
Fixed Method for sorting the hashes, so that the ldap hash can be sorted too. If the order of the hash elements in ldap changes at every puppet run, every time a reconfigure and a restart of the gitlab will be triggered.