controller_configuration VS ansible.utils

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.

We're happy to announce the following networking collection updates: * ansible.utils 2.8.0 has been released with new features (changelog) * cisco.iosxr 4.0.3 has been released with bugfixes (changelog) * cisco.nxos 4.0.1 has been released with bugfixes (changelog) * junipernetworks.junos 4.1.0 has been released with new features (changelog)

The ipaddr filters are broken in ansible.netcommon 2.6.0 release as we have recently migrated ipaddr filters from ansible.netcommon to ansible.utils. We have released utils 2.5.2 and netcommon 2.6.1 which fixed these two issues (ansible.netcommon#375, ansible.utils#148). For the FQDN issue, the ansible-core team has already merged the fix. This fix will be available in the March 28th release, which means that users of non fqdn ipaddr filters can use the old netcommon collection version 2.5.1 as a workaround until the next ansible-core release (March 28th) by the core-team. For fqdn ipaddr filters, users can use the latest versions of any of ansible.netcommon (2.6.1) or ansible.utils (2.5.2).

We hope you'll enjoy part1 and part2, and take a look at the collection and source repo where we'd love to hear your suggestions on how to improve the collection.

Also handy for this and other IP related tests, the Ansible.utils collection https://github.com/ansible-collections/ansible.utils /u/CertifiedKnowNothing

See: https://www.ansible.com/blog/using-new-ansible-utilities-for-operational-state-management-and-remediation https://github.com/ansible-collections/ansible.utils/blob/main/plugins/sub_plugins/cli_parser/ttp_parser.py

Also, I've not done it this way, but I believe this could be short-cut even further using: https://github.com/ansible-collections/ansible.utils/blob/main/plugins/sub_plugins/cli_parser/ttp_parser.py#L23-L28