add support of task's targets set directly in playbook #85
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.
Add new task-level filed
targets
.It will be used only in case no
-t/--target
is set in the command line. Technically,-t
always set as it has a default targetdefault
; however, this PR considers such default as non-set and will use task.targetsThis is what it looks like in the playbook:
targets inside the task resolved the same way as targets defined in the command line, i.e. all the sequence of matching groups, tags, names, etc...
The reason why this may be handy is the ability to make a playbook with multiple tasks where all the tasks are sort of related but should be running on a different subset of hosts. For instance, one task deploys changes to the master/controller boxes, and another task deploys to working nodes.
Before this change, It was possible to run the spot twice for different task with different targets or even different playbooks. However, for related tasks, it is very nice to have a single
spot
run dealing with everything