Actions
Story #6458
closed
Task #6432: [Epic] ansible-pulp backlog
As a user, I can consume pulp_installer as a collection from Ansible Galaxy
Start date:
Due date:
% Done:
100%
Estimated time:
(Total: 0:00 h)
Platform Release:
Groomed:
No
Sprint Candidate:
Yes
Tags:
Sprint:
Quarter:
Description
After some scoping, this will involve:
- Creating galaxy.yml
- GitHub Actions publishing via the ansible-galaxy command, using a user-account's galaxy token as a GHA secret (we cannot use a specific service token or organization token) [1] [2] [3]
- Renaming roles to use underscores rather than dashes
- Replacing the directory structure for our example-use and example-source playbooks and vars files, including the CI scripts that modify them (like for pulp_rpm_prerequisites) and pulplift that calls them (compat symlinks might be appropriate.)
- Updating docs & references, for the new process of downloading, and for #4.
[1] https://www.jeffgeerling.com/blog/2020/automatically-building-and-publishing-ansible-galaxy-collections [2] https://github.com/ansible/galaxy/issues/2070 [3] https://github.com/ansible-collections/kubernetes/issues/43
Related issues
Actions
.
Rename ansible-pulp to pulp_installer
This helps avoid confusion with pulp-ansible, and makes the name valid (no dashes) for publishing to galaxy as a collection.
fixes: #6406 Rename ansible-pulp to pulp_installer https://pulp.plan.io/issues/6406
re: #6458 As a user, I can consume pulp_installer as a collection from Ansible galaxy https://pulp.plan.io/issues/6458