Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/pulp/pulp_ansible

A Pulp plugin that manages Ansible content, i.e. roles, collections
https://github.com/pulp/pulp_ansible

ansible collections galaxy pulp roles

Last synced: 8 days ago
JSON representation

A Pulp plugin that manages Ansible content, i.e. roles, collections

Awesome Lists containing this project

README

        

pulp_ansible
============

.. figure:: https://github.com/pulp/pulp_ansible/actions/workflows/nightly.yml/badge.svg?branch=main
:alt: Ansible Nightly CI/CD

A Pulp plugin to support hosting ``Role`` and ``Collection`` Ansible content.

For more information, please see the `documentation `_.

Collection Support
------------------

.. warning::

The 'Collection' content type is currently in tech-preview. Breaking changes could be introduced
in the future.

pulp_ansible can manage the `multi-role repository content `_ referred to as a `Collection`. The following features are
supported:

* `ansible-galaxy collection publish` - Upload a Collection to pulp_ansible for association with one or more
repositories.
* `ansible-galaxy collection install` - Install a Collection from pulp_ansible.

Configuring Collection Support
------------------------------

You'll have to specify the protocol and hostname the pulp_ansible REST API is being served on. For
pulp_ansible to interact with `ansible-galaxy` correctly it needs the entire hostname. This is done
using the `ANSIBLE_HOSTNAME` setting in Pulp. For example if its serving with http on localhost it
would be::

export PULP_ANSIBLE_API_HOSTNAME='http://localhost:24817'
export PULP_ANSIBLE_CONTENT_HOSTNAME='http://localhost:24816/pulp/content'

or in your systemd environment::

Environment="PULP_ANSIBLE_API_HOSTNAME=http://localhost:24817"
Environment="PULP_ANSIBLE_CONTENT_HOSTNAME=http://localhost:24816/pulp/content"

How to File an Issue
--------------------

`New pulp_ansible issue `_.

.. warning::
Is this security related? If so, please follow the `Security Disclosures `_ procedure.