For awhile, the Red Hat Ansible team behind the components Ansible automation hub and Ansible cloud automation hub at console.redhat.com have been on a special ops mission to enhance the galaxy_ng code base that serves the aforementioned components to also serve galaxy.ansible.com, with the intention of replacing galaxy.ansible.com with a fresh code base.
Galaxy, a legacy far far away…
The current Galaxy service has been running at galaxy.ansible.com for many years and is hugely successful in the community. It drives and nurtures Ansible adoption by sharing prebuilt Ansible content that solves many automation challenges.
One of the statistics we are most proud of are the contributions of 33,965 individual automation answers by the community in either Ansible Content Collections or Ansible Roles. Some of the top ranking automation content includes AWS, VMware, Linux, and Windows. Community users are able to download content for free, self-supported and interact with authors via GitHub for any further help or enhancements.
We are excited to announce that the galaxy.ansible.com code base is being updated with a host of exciting new features that the Ansible community can look forward to. Brought to you by the Red Hat Ansible team behind Ansible Automation Hub and Ansible Cloud Automation Hub on console.redhat.com, this new version will enhance the galaxy_ng code base that also serves the above listed components.
As galaxy.ansible.com ages, the frameworks it sits on requires consistent maintenance for security vulnerabilities, including frequent patching. The team is committed to keeping Galaxy secure and high-functioning, so we set out to enable Galaxy with an automation hub, otherwise known as the galaxy_ng codebase. […]
You are welcome to comment on the topic here and keep reading the article in the Ansible blog below:
To all who have commented here, we are going to be splitting the comments from this thread to their own thread to make it easier for the @galaxy team to address them. Please allow us some time while we do that.
We will also lock this topic to new comments to avoid mixing issues, and request everyone who needs help with the new Galaxy NG at galaxy.ansible.com to open a new topic doing the following:
title it with a brief description of your issue, for ex. “my galaxy.ansible.com namespace is broken” or “galaxy.ansible.com api is failing with an error”.
tag it with galaxy-ng for the Galaxy team to be aware of it
add all the details possible on the issue you are having, please use code blocks if you are pasting an error or playbook to help with readability.
