This project provides an integration between Visual TOM and Ansible to execute Playbook with options or not.
No Support and No Warranty are provided by Absyss SAS for this project and related material. The use of this project's files is at your own risk.
Absyss SAS assumes no liability for damage caused by the usage of any of the files offered here via this Github repository.
Consultings days can be requested to help for the implementation.
- Visual TOM 7.1.2 or greater
- python3
- ansible
- ansible-runner
You need the Python add-on module ansible-runner. To install it, run the following commands using the provided requirement.txt file:
pip install -U update
pip install -U -r requirement.txt
The ansible.xml template must be imported into VTOM. It contains 5 parameters to be filled in (mandatory or optional):
- The working directory containing the playbook(s) (mandatory)
- The name of the playbook to execute (.yml) (mandatory)
- The inventory file (full path) (optional)
- Extra variables (optional)
- Tags (optional)
The Python script ansible.py is executed from the queue batch tom_submit.ansible. Provide the full path to the ansible.py script in the queue batch. If the script is located in $TOM_SCRIPT, no changes are required.
Line 31 : python3 ${TOM_SCRIPT}/ansible.py
It is possible to execute Ansible playbooks by specifying mandatory and optional arguments.
The main action is to execute an Ansible Playbook by providing the following mandatory inputs:
- Playbook Path: The directory containing the playbook(s)
- Playbook: The playbook to execute
- option: -i (inventory)
- Uses a custom Ansible inventory
- Allows targeting different environments (prod, preprod, etc.)
- option: -e (extra vars)
- Injects Ansible variables (extra_vars)
- Allows modifying the playbook behavior without changing it
- option: -t (tags)
- Executes only tagged tasks / roles
- Useful for targeted operations (patch, restart, deploy…)
This project is licensed under the Apache 2.0 License - see the LICENSE file for details
Absyss SAS has adopted the Contributor Covenant as its Code of Conduct, and we expect project participants to adhere to it. Please read the full text so that you can understand what actions will and will not be tolerated.
