Sorin Sbarnea ssbarnea@redhat.com writes:

It raised to my concern that sometimes we need to pass some tags (or skip-tags) to ansible playbooks or roles.

At this moment there is no support for this in zuul but there is an older CR that would add it: https://review.opendev.org/#/c/575672/ (will need few changes)

Since that review was created we already got a "tags" feature in zuul, which was initially purposed for categorization on jobs.

Minor clarification: 'tags' has been around much longer than that change. I only mention it so that folks don't think we ignored that and implemented something else.

I would like to redefine the meaning of current "tags" feature and document the fact that these would also be passed to ansible.

I do not think that categorization conflicts with passing tags to ansible but is better to ask.

If we do this we will be able to use "tags" and "skip-tags" just the same way we do in Ansible and avoid the case where our params are different than ansible ones.

I think this is reasonable. I did a quick search on codesearch.openstack.org, and the only use of the Zuul tags field I can find is in zuul-jobs (the feature that we use to auto-generate jobs). I think that's still compatible with this.

But if anyone else is using Zuul's tags field, please let us know. :)

-Jim