Filter by TAGS feature about semaphore

[twhiston]

@lfalcao I know this is from a really long time ago, but this is a cool feature. Would you still be interested in making it work and making a PR against the current develop branch?

[lfalcao]

@bence-takacs,

We're doing some tests with semaphore and this is a important feature to have. So i've added a basic support to tags on my fork. (lfalcao@1520769)

[bence-takacs]

Thanks! I will look into it!

[lfalcao]

@twhiston I can't. I'm not using it anymore and i'm out of time...

[strangeman]

In our environment, we just pass tags in Extra CLI arguments. If we add separate Tags field - how we will merge these two sources of tags together?

[twhiston]

I guess we would need to merge at runtime, which wouldn't be too terrible, but none the less it is overhead, and then we have to deal with things like which takes precedence. I like the explicitness of having tags in a field but perhaps it makes the extra cli arguments less clear and that is seems problematic. What do you think?

Out of interest (this is slightly unrelated but it seems appropriate to mention here) how do you rerun a failed playbook with semaphore in your workflow?

[strangeman]

We can use "Override semaphore arguments" checkbox for this. If it checked - tags takes from the 'Extra CLI' field, if not - from the form.
Or, we can just pass all tags to Ansible, since 2.4 it will merge all --tags options together: https://github.com/ansible/ansible/blob/stable-2.4/CHANGELOG.md#deprecations

If playbook failed, we just get the message to the team Telegram chat and somebody fix it. :)