fix: deploy exception playbooks always on all hosts #608
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
SteBaum
force-pushed
the
stephan/fix/deploy-all-nodes
branch
from
78761c9 to
397a1fc
Compare
PaulFarault
reviewed
Oct 18, 2024
There was a problem hiding this comment.
Let's discuss about the way we could solve this issue with @rpignolet at next meeting.
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.
Which issue(s) this PR fixes
Fixes None
Additional comments
This is one approach to solve the issues of playbooks which always have to be deployed on all hosts even if only a specific one is set in the command. It is the case for the following playbooks in the tdp collection:
Agreements