Release 0.26.0 - #216
Merged
Merged
Conversation
This file contains hidden or 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
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.
Bumps
Cargo.tomlto 0.26.0 and dates theUnreleasedsection. Tag follows the squash merge.Minor, not patch: #215 changes where a declarative merge writes a value the source declares on a group. Through Ansible the per-host answer is unchanged, but a consumer reading
_meta.hostvarsdirectly now finds it on the group instead. Pre-1.0, that belongs in the minor.What is in it
#215 — group vars are carried onto the target's groups, not onto each host. 0.25.0 taught the merge to find a field declared on a group and then wrote it onto every member: a value shared by 780 machines cost 780 entries, the same duplication 0.25.0 had just removed from the static-inventory connector. It is now merged onto the target's group of the same name, one copy, and the consumer resolves it with its own precedence.
allneeds no matching name, since in Ansible it means every host — and the mergedallcarries the target's hostnames, because an endpoint drops a group with neither hosts nor children and the variables would otherwise be rendered away without a word.A field declared on a host is still copied onto that host.
fieldsfilters both paths. No host crosses between sources.