I have praised Ansible tags all about the previous post. Unfortunately, tags don't go along with Ansible Tower complex workflows. Let me guide you through the playbook transformation we've done. The answer to this challenge is extra variables.
Practically, it's the only answer for now if you want to keep the same functionality for Ansible and Ansible Tower. You can define it as an extra variable or add a user survey and pass it down to all jobs in the workflow.
Let's get the example from the previous piece and sprinkle it with that extra variables support. Modified playbook tries to use an external tower_operation variable or uses 'start' or 'stop' values if the variable is undefined.
Now you have more options to control playbook execution:
From the command line with tags, for example --tags stop.
From the command line with extra variable -e "tower_operation='stop'".
Declare an extra variable for the Ansible Tower Workflow as a survey or extra variable.