[PR #597/74b2c95d backport][stable-2.14] Add details of interactions between notifications and loops #2064
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
* Add details of interactions between notifications and loops This clarifies behaviour raised in ansible/ansible#81950 and ansible/ansible#77550 as expected and documented. * Apply suggestions from code review Co-authored-by: Maxwell G <[email protected]> * Incorporate suggestions from @felixfontein Make the loop trigger even more explicit. --------- Co-authored-by: Sandra McCann <[email protected]> Co-authored-by: Maxwell G <[email protected]> (cherry picked from commit 74b2c95)
oraNod
approved these changes
Oct 25, 2024
oraNod
deleted the
patchback/backports/stable-2.14/74b2c95dd4a13db21b167de9bb72f7287f679841/pr-597
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This is a backport of PR #597 as merged into devel (74b2c95).
This clarifies behaviour raised in ansible/ansible#81950 and ansible/ansible#77550 as expected and documented.