You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ansible treats this as two separate runs which show up separately on ARA. All fine until here. However while the first run as the following labels: check: False, tags:all, subset:host1, default_label, the second run only gets default_label.
By default_label I mean the one I have set in ansible.cfg with default_labels =
Tested with ara 1.7.1
What should be happening ?
Ideally the labels would be the same for both playbooks
The text was updated successfully, but these errors were encountered:
That is a curious behavior indeed. I suppose if you run the two playbooks separately the labels are picked up properly ?
Yes indeed. Running playbooks as normal has no issues, even if those playbooks include other playbooks etc
This is probably not the most common use case, but I use it from time to time, as we have some playbooks which are named like do-thing-1, do-thing-2 etc which I can quickly call with do-thing*.
What is the issue ?
First of all thank you for developing ARA. It's great.
I noticed the following issue (not super important but I figured I should report it anyway).
When running the following command:
ansible
treats this as two separate runs which show up separately on ARA. All fine until here. However while the first run as the followinglabels
:check: False, tags:all, subset:host1, default_label
, the second run only getsdefault_label
.By
default_label
I mean the one I have set inansible.cfg
withdefault_labels =
Tested with ara 1.7.1
What should be happening ?
Ideally the labels would be the same for both playbooks
The text was updated successfully, but these errors were encountered: