Release 0.27.0 - #219
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
1 participant
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.27.0, dates theUnreleasedsection, and adds its compare link. Tag follows the squash merge.Minor, not patch: #218 inverts what an absent
fieldsmeans on a declarative enricher — from taking nothing to taking everything. No live enricher is affected (all six name their fields), but that is the largest possible swing in what a given config does, and pre-1.0 that belongs in the minor.What is in it
#218 — absent
fieldstakes every var. It meant the empty set, so an enricher with asource_id, atarget_idand nofieldsran, copied nothing and reported success. It also did not match the thing it models: being in a group carries all of that group's vars in Ansible, with no per-name permission.fieldsis the narrowing; its absence now means the ordinary thing.fields: []is unchanged and still takes nothing — an explicitly empty list names nothing, which is a different statement from not naming any.No host crosses between sources: taking every var is not taking hosts.