Good afternoon -
We have a playbook that is used by multiple groups. This playbook is neutrally stored and run from a common area. How can we, for lack of a better term, label the job at run time so that we can associate it to the PROJECT that is executing it. And even better, how can we include a variable from the playbook (ie. ENV) as a searchable item?
Ideally - I would search in the “Jobs” for myproject myenv CommonTool
Example
ABC DEV JBOSS
- This would show me all the deployments for the project ABC to the DEV environment for MIDDLEWARE TOOL JBOSS.
Thanks in advance for any help you can provide!!
Good afternoon -
We have a playbook that is used by multiple groups.
What is a "group"?
This playbook is neutrally stored and run from a common area.
So, some sort of network share?
How can we, for lack of a better term, label the job at run time so that we
can associate it to the PROJECT that is executing it.
Well, how is that PROJECT defined? Is it part of the login credentials of the
user running the playbook?
Let's leave ansible aside for a moment - what's the simplest way you can think
of in your login environment to identify the PROJECT under which *any* command
gets run?
PS: I also notice that you are asking about Ansible Tower, which has its own
paid support mechanism, whereas you are here asking for help in the community
ansible project, which is separate, and most people here are not going to be
familiar with Ansible Tower, so unless your question is generic to both
environments, this may not be the best way to get the support you require.
Some of my questions above may easily fall into this category, since I have no
clue myself about Ansible Tower.
Antony.
sorry, groups… I mean just multiple groups in the organization…
Neutrally stored (in GitHub).
The project actually has a variable associated to them. In addition, there is also an ENVIRONMENT variable getting set in the playbook.