Pure1-Collection
galaxy_collection
Pure1-Collection | galaxy_collection | |
---|---|---|
2 | 6 | |
1 | 51 | |
- | - | |
6.4 | 8.3 | |
6 days ago | 4 days ago | |
Python | Python | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Pure1-Collection
-
The Bullhorn #108 (Ansible Newsletter)
purestorage.pure1 has been released with features and bugfixes (changelog).
-
The Bullhorn #89 (Ansible Newsletter)
purestorage.pure1 1.1.0 (changelog) has been released.
galaxy_collection
-
The Bullhorn #114 (Ansible Newsletter)
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.
-
Multiple collections in one repo.
Reddit hates mobile format, here is link https://github.com/redhat-cop/ah_configuration/blob/devel/tests/playbooks/ah_configs/ah_collections.yml
-
Ansible Collection ideas (UNI thesis)
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 Bullhorn #89 (Ansible Newsletter)
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
-
Triggering Collection sync on github PR?
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.
-
The Bullhorn #82 (Ansible Newsletter)
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.
What are some alternatives?
junipernetworks.junos - Ansible Network Collection for Juniper JunOS
controller_configuration - A collection of roles to manage Ansible Controller and previously Ansible Tower
ansible.netcommon - Ansible Network Collection for Common Code
playbooks
cisco.ios - Ansible Network Collection for Cisco IOS
ee_utilities - This ansible collection includes a number of roles and tools which can be useful for managing Ansible Execution Environments.
creator-ee - Ansible Execution environment targeted for content creators. It includes most development tools such ansible-lint, molecule, ...
community.vmware - Ansible Collection for VMware
community-topics - [Moved to Ansible Forum] Discussions for Ansible Community Meetings
ansible-collection-vultr
ansible-creator - The fastest way to generate all your ansible content!