This Ansible collection extends the infra.aap_configuration collection by providing extra functionalities that allows advanced operations on the Ansible Automation Platform Configuration as Code.
We are on the Ansible Forums and Matrix, if you want to discuss something, ask for help, or participate in the community, please use the #infra-config-as-code tag on the form, or post to the chat in Matrix.
The awx.awx or ansible.controller collections MUST be installed in order for this collection to work. It is recommended they be invoked in the playbook in the following way.
---
- name: Playbook to configure ansible controller post installation
hosts: localhost
connection: local
vars:
controller_validate_certs: true
collections:
- awx.awx| Collection Name | Purpose |
|---|---|
| ansible.platform repo (no public repo for this collection) | gateway/platform modules |
| ansible.hub repo | Automation hub modules |
| ansible.controller repo | Automation controller modules |
| ansible.eda repo | Event Driven Ansible modules |
| Collection Name | Purpose |
|---|---|
| AAP Configuration | Easy interaction with Ansible Automation Platform via Ansible roles |
| EE Utilities | Execution Environment creation utilities |
| AAP installation Utilities | Ansible Automation Platform Utilities |
| AAP Configuration Template | Configuration Template for this suite |
Click the Content button to see the list of content included in this collection.
You can install the infra.aap_configuration_extended.collection with the Ansible Galaxy CLI:
ansible-galaxy collection install infra.aap_configuration_extendedYou can also include it in a requirements.yml file and install it with ansible-galaxy collection install -r requirements.yml, using the format:
---
collections:
- name: infra.aap_configuration_extended
# If you need a specific version of the collection, you can specify like this:
# version: ...The awx.awx or ansible.controller collection must be invoked in the playbook in order for Ansible to pick up the correct modules to use.
The following command will invoke the collection playbook. This is considered a starting point for the collection.
ansible-playbook infra.aap_configuration_extended.configure_controller.ymlOtherwise it will look for the modules only in your base installation. If there are errors complaining about "couldn't resolve module/action" this is the most likely cause.
- name: Playbook to configure ansible controller post installation
hosts: localhost
connection: local
vars:
controller_validate_certs: true
collections:
- awx.awxDefine following vars here, or in controller_configs/controller_auth.yml
aap_hostname: ansible-controller-web-svc-test-project.example.com
You can also specify authentication by a combination of either:
aap_hostname,aap_username,aap_passwordaap_hostname,aap_oauthtoken
The OAuth2 token is the preferred method. You can obtain the token through the preferred controller_token module, or through the
AWX CLI login
command.
These can be specified via (from highest to lowest precedence):
- direct role variables as mentioned above
- environment variables (most useful when running against localhost)
- a config file path specified by the
controller_config_fileparameter - a config file at
~/.controller_cli.cfg - a config file at
/etc/controller/controller_cli.cfg
Config file syntax looks like this:
[general]
host = https://localhost:8043
verify_ssl = true
oauth_token = LEdCpKVKc4znzffcpQL5vLG8oyeku6Controller token module would be invoked with this code:
- name: Create a new token using controller username/password
awx.awx.token:
description: 'Creating token to test controller jobs'
scope: "write"
state: present
controller_host: "{{ aap_hostname }}"
aap_username: "{{ aap_username }}"
aap_password: "{{ aap_password }}"
Every Ansible Controller instance has it's own particularities and needs. Every administrator team has it's own practices and customs. This collection allows adaptation to every need, from small to large scale, having the objects distributed across multiple environments and leveraging Automation Webhook that can be used to link a Git repository and Ansible automation natively.
A complete example of how to use all of the roles present in the collection is available at the following README.md, where all the phases to allow CI/CD for the Controller Configuration are provided.
The input data can be organized in a very flexible way, letting the user use anything from a single file to an entire file tree to store the controller objects definitions, which could be used as a logical segregation of different applications, as needed in real scenarios.
The awx command line can export json that is compatible with this collection. In addition there is an awx.awx/ansible.controller export module that use the awx command line to export. More details can be found here
A Template to use in order to start using the collections can be found here
- Ansible Using collections for more details.
For details on changes between versions, please see the changelog for this collection.
This collection follows Semantic Versioning. More details on versioning can be found in the Ansible docs.
We plan to regularly release new minor or bugfix versions once new features or bugfixes have been implemented.
Releasing the current major version happens from the devel branch.
Adding the ability to use direct output from the awx export command in the roles along with the current data model.
We welcome community contributions to this collection. If you find problems, please open an issue or create a PR against the Controller Configuration collection repository. More information about contributing can be found in our Contribution Guidelines.
We have a community meeting every 4 weeks. Find the agenda in the issues and the calendar invitation below:
This collection follows the Ansible project's Code of Conduct. Please read and familiarize yourself with this document.
GNU General Public License v3.0 or later.
See LICENSE to see the full text.