This repository has been archived by the owner on Mar 6, 2023. It is now read-only.
Retain order in yaml dictionaries #380
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
github-actions
bot
added
area/jinja
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 group_vars, the scrape_configs are nicely formatted with job_name at the top. That is clear and readable.
Then, you run ansible and it generates the prometheus.yml file. The resulting scrape configs are jumbled. They lose the previous ordering.
The solution is adding
sort_keys=Falseto the to_nice_yaml filter.References:
yaml/pyyaml#110
ansible/ansible#76638