New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Validate task attributes with first finalized attrs after loop #80476
Merged
s-hertel
merged 5 commits into
ansible:devel
from
s-hertel:fix-post-validating-tasks-with-loops
Apr 13, 2023
+15
−5
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
48cca24
Validate task attributes with first finalized attrs after individual …
s-hertel f74f3bd
changelog
s-hertel 342355c
use last loop info?
s-hertel fbdd58f
Fix ignore_unreachable, which suffered from the same issue as run_onc…
s-hertel 1ee5284
fix action too
s-hertel File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
bugfixes: | ||
- Fix post-validating looped task fields so the strategy uses the correct values after task execution. |
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was worried
self._task.from_attrs(task_fields)
might cause issues, so I tried to identify all the FieldAttributes potentially affected by this issue. I believe it's limited to the fieldsaction
,run_once
,ignore_unreachable
,ignore_errors
,loop
, andno_log
since these may be used after the looped task is executed.no_log
is fine, because it's set just above this changeloop
is fine because empty loops == skipped task and the codepath with the issue (template string is always truthy) doesn't occurignore_errors
is fine because the value for the Task is set to False if any of the individual items are FalseSo I fixed
ignore_unreachable
using the same pattern asignore_errors
, and limited this to just setrun_once
andaction
.