Draft: Allow to change group names used in conditions to be able to use with bigger inventories #105
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 draft tries to solve the issue that in all conditions etc, there are used generic group names, even 'all'.
If you attempt to use an inventory that has also other hosts in other groups, the counting of nodes is failing and eg one node clusters don't trigger their one-node specific tasks.
I've created a way to rename the gropus used in
when:
and simmilar conditions. Note that this is NOT possible forhosts:
in a play, because it will not pull the value from group_vars. So if you want to run it against only one cluster, you still need to use-l name_of_the_cluster_all_group
So far it's tested only on one node clusters, so more testing needs to be done, but at least it allows to coexist with other playbooks with one inventory and multiple clusters should work. You just need to add the specific groups to the generic one, because of the
hosts:
, eg.and then you remap it in the
group_vars/kube_lab_cluster
like this (and analogically ingroup_vars/kube_prod_cluster
)