-
Notifications
You must be signed in to change notification settings - Fork 144
RelEng: ansible collections
- What credentials do you need?
- Commit to the collection repo?
- ask who?
- A token to upload to galaxy?
- who do we ask to be authorized?
- Link to where to get the token?
- What file do we drop the token into?
- Commit to the collection repo?
# Fresh checkout so that no unnecessary artifacts are included:
git clone [email protected]:ansible-collections/$COLLECTION_NAME
# update version string in galaxy.yml
vim galaxy.yml
# Build the tarball
ansible-galaxy collection build
time ansible-galaxy collection publish community-NAME-VERSION.tar.gzIf you configure Zuul for your project, it can do this based on tagging events:
https://github.com/ansible/zuul-config#on-board-new-repo-into-zuul
This Wiki is used for quick notes, not for support or documentation.
Working groups are now in the Ansible forum
Ansible project:
Community,
Contributor Experience,
Docs,
News,
Outreach,
RelEng,
Testing
Cloud:
AWS,
Azure,
CloudStack,
Container,
DigitalOcean,
Docker,
hcloud,
Kubernetes,
Linode,
OpenStack,
oVirt,
Virt,
VMware
Networking:
ACI,
AVI,
F5,
Meraki,
Network,
NXOS
Ansible Developer Tools:
Ansible-developer-tools
Software:
Crypto,
Foreman,
GDrive,
GitLab,
Grafana,
IPA,
JBoss,
MongoDB,
MySQL,
PostgreSQL,
RabbitMQ,
Zabbix
System:
AIX,
BSD,
HP-UX,
macOS,
Remote Management,
Solaris,
Windows
Security:
Security-Automation,
Lockdown
Tooling:
AWX,
Galaxy,
Molecule
Plugins:
httpapi