Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation on publishing to Galaxy updated. #1123

Merged
merged 1 commit into from
Nov 13, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/PUBLISHING_TO_GALAXY.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@
2. Create new Release pointing to new X.Y.Z tag https://github.com/ansible-collections/community.zabbix/releases

Additional manual steps are required when automatic publish to Ansible Galaxy is not enabled in the repository. This
requires a user who has access to the `community.zabbix` namespace on Ansible Galaxy to publish the build artifact.
requires a user who has access to the `community` namespace on Ansible Galaxy to publish the build artifact.

3. Run the following commands to build and release the new version on Galaxy:

Expand All @@ -38,4 +38,6 @@ requires a user who has access to the `community.zabbix` namespace on Ansible Ga
ansible-galaxy collection publish ./community-zabbix-$VERSION_HERE.tar.gz
```

4. If 3. is not feasible for any reason then create a post in "Get Help" section of Ansible forum https://forum.ansible.com/c/help/6/none so somebody from admins can take a look and see/fix why new version has not been published to Galaxy (e.g. https://forum.ansible.com/t/access-to-collection/2295/4).

After the version is published, verify it exists on the [Zabbix Collection Galaxy page](https://galaxy.ansible.com/community/zabbix).