Publishing Ansible Collections to Ansible Galaxy and Automation Hub

How to distribute our custom Ansible Collection to Ansible Galaxy and Automation Hub.

Introduction

Ansible Collections provides a structured way to package and distribute Ansible content, offering a modular and organized approach to automation. Collections typically include modules, plugins, roles, and playbooks that address specific use cases. In this article, we’ll delve into the process of distributing Ansible Collections, covering key aspects such as configuring distribution servers, building tarballs, and publishing collections.

Distribution Servers

Before distributing an Ansible Collection, you need to choose a distribution server. The prominent options include:

1. Ansible Galaxy: Supports all collections and is widely used for community-driven content.
2. Pulp 3 Galaxy: Similar to Ansible Galaxy but with added support for signed collections.
3. Red Hat Automation Hub: Specifically for Red Hat-certified collections, with support for signed collections.
4. Privately Hosted Automation Hub: Enables distribution of collections authorized by the owners.