ansible-build-data VS controller_configuration

IBM -> RedHat -> Ansible (https://docs.ansible.com/platform.html)

I think the new ansible docs are opaque, and the new "everything is an ansible collection" scheme makes troubleshooting any issues reported by users hundreds of times harder than "the old days"

I keep this (https://github.com/ansible-community/ansible-build-data/blob...) bookmarked because it's the only way to match up what "ansible 8.1.0" (https://pypi.org/project/ansible/8.1.0/) even means since it for damn sure not any of this: https://github.com/ansible/ansible/releases (they used to have a 'release' pinned on that releases tab saying "these are not the droids you are looking for"). I believe I tried asking for them to update the completely erroneous pypi "source code" link to point to that repo and ... well, one can see how well that turned out

➡️ Check Release Notes📦️🗒️ and Ansible 8 Porting Guide for more details.

💽You can install it by running the following command or download the release tarball directly from pypi: pip install ansible==8.0.0a1 --user ➡️Check Release Notes 📦️🗒️ and Ansible 8 Porting Guide for more details!

You can find the current list for Ansible 7 here: https://github.com/ansible-community/ansible-build-data/blob/main/7/ansible-7.build

Check Release Notes📦️🗒️ and Ansible 6 Porting Guide for more details on changes, improvements, new and deprecated features!!

You can find the release announcement on ansible-announce and the changelog on GitHub. Happy automating!

The vmware.vmware_rest collection has been included in Ansible 5. Thanks to everyone involved!

As https://github.com/ansible-community/ansible-build-data/issues/114 showed we should really check the existing collections included in the Ansible package. Some ideas:

Ansible 5.7.0 has been released with updates to 19 of the included Ansible collections! Read the announcement or check out the update changelog to learn more about this new version.

Debian package "ansible" -> called "ansible" on PyPI -> is called "ansible collections" through most of the documentation -> upstream PyPI packages are generated through https://github.com/ansible-community/ansible-build-data

infra.controller_configuration 2.5.1 has been released. This Ansible collection allows for easy interaction with an AWX or Ansible Controller server via Ansible roles using the AWX/Controller collection modules.

The controller_configuration collection version 2.4.0 has been released.

The Infra config as Code collection group will have a Public Office hours meeting on May 11th at 9am EST/1pm UTC. Details here.

one thing is to play to what you know. Also know that collections can be roles, modules, or both. A few biased collections to look at to see the difference would be infra.controller_configuration - a set of roles to implement either the awx.awx collection or ansible.controller collection for doing configuration as code.

multiple collections with grouped roles, then playbooks to execute those roles as needed. You can also do role include like dispatch here to make it more flexible.

The infra collections have had recent updates: * infra.ah_configuration 1.1.0 Automation hub and galaxy_ng configuration. Majorly improved testing and as a result of fixes all modules and roles work on the last 3 versions of galaxy_ng and Automation Hub. * infra.controller_configuration 2.2.5 Various fixes and additions and improvements to collection, including methods to export configuration files from controller to be used by the collection. * infra.ee_utilities 2.0.6 Updated several bugs and add ability to use types in collection requirements for building execution environments

All of the collections in this group have recently released changes. This includes: * infra.controller_configuration 2.1.9 released to be compatible with recently added AWX changes. Changelog here. * infra.ah_configuration 0.9.2 Automation hub and galaxy_ng configuration. Fixed various major errors, including a major publishing error. Changelog here. * infra.ee_utilities 2.0.1 Updated to add several use cases to Execution Environment Creation. * infra.aap_utilities 2.2.2 Update to OCP installer to allow individual components.

For the server configuration, its on the kubernetes side, however for the AWX configuration of projects, job templates, credentials and the like is the redhat_cop.controller_configuration collection. It uses the awx.awx collection or the ansible.controller configuration to interact with the API to manage things in AWX. The collections are built to work with Ansible Automation Controller, but 99.9% of the time its going to work with AWX.