ansible-inclusion VS galaxy_collection

The new collection inclusion requests are waiting for your reviews. Please help the community extend the package!

quantumsheep.scaleway

The vultr.cloud colletion has passed the Colletion inclusion procedure and will be included in the next minor release of Ansible 6.

grafana.grafana

dellemc.unity

We will be sorting out the requests in the following categories: * second review needed * new collection reviews

inspur.ispim

The inspur.ispim collection inclusion request is waiting for your review. See the process description to learn how to do it.

The following collection inclusion requests are waiting for your review: * vultr.cloud * check_point.gaia * purestorage.fusion

Inclusion requests to review: * ibm.spectrum_virtualize * purestorage.fusion * vultr.cloud * check_point.gaia * inspur.ispim

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.