We want to allow users to create they own collection under company namespace, but not sharing with the rest of the Hub users
- Create a Automation Hub group, but not adding any role to it.
- Assign the user to the group. For example,
- Create a private Automation Hub repository. Make sure
Create Distributioncheck box is selected. Set
None, otherwise the approval process will publish to the public
- Go to
Accesstab of the created repository, select the group created above
galaxy.ansible_repository_ownerrole on the next step, and then click
We can add exisiting collection under the
Collection versionstab, but we will push a new collection via command line. Copy the info from the pop-up window by clicking
Copy CLI configurationbutton on top right. Update the
ansible.cfgfile with this new repo info.
[galaxy] server_list = developer_repo [galaxy_server.developer_repo] url=https://aap-hub1.lab.automate.nyc/api/galaxy/content/developer_repo/ token=my_token
- Create the namesapce
automate_nycfor our collection.
- Under the
Accesstab of the created namespace, select the created group from above
- Select both
galaxy.collection_publisherto give the group full access to the repository content
- With the updated
developer_repo, push the collection using
ansible-galaxy collection publish automate_nyc-test-1.0.5.tar.gz
- Verify the collection under the repository
- But we won’t be able to see it under
automate_nycnamespace because the
Hide from searchoption of the repository
- Other Hub users won’t be able to see the repository or collection neither.
- To use the collection in AAP, we will need to add a
Ansible Galaxy/Automation Hub API Tokenspecificly for this repository, similar to what we added to
ansible.cfg, and assign to the organization