ansible-podman-collections VS galaxy_collection

I'm using the podman ansible module[1] to manage the podman container atm, it's ... Okish. I wrote a spaghetti mess with ansible conditionals and loops to manage multitude of systemd files made from podman-generate-systemd. If I had some time maybe I'll try this out, a more declarative approach would certainly be nicer.

[1]: https://github.com/containers/ansible-podman-collections

New version 1.10.0 of Ansible Podman collection was released. We have a lot of bugfixes and improvements, a new become plugin - podman_unshare which allows user to execute commands in its container user namespace, and a new module - podman_generate_systemd for Systemd unit files generation for containers and pods.

containers.podman collection released new 1.9.1 version, since last update we have new podman_tag module, also updated module podman_secret which manages secrets for Pods and options for newest Podman Pod versions.

use the source: https://github.com/containers/ansible-podman-collections

infra.ah_configuration 2.0.2 has been released. This Ansible collection allows for easy interaction with an Galaxy NG or Ansible Automation Hub via Ansible modules and roles.

Reddit hates mobile format, here is link https://github.com/redhat-cop/ah_configuration/blob/devel/tests/playbooks/ah_configs/ah_collections.yml

infra.ah_configuration - a set of roles and modules that was built on the skeleton of the code of awx.awx to manage Automation Hub/galaxy_ng.

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

Generally we don't publish a new collection every PR, you can do that, but we have not. We treat them as releases, the Version number needs to be changed, updated, and a collection needs to made with ansible-galaxy collection build. We do this through a release pipeline that triggers on release, but we use a templates galaxy file, that gets processed, and then build and publishes the resulting collection. An example of this that I ran last night can be found here.

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.