Migrated this issue from github galaxy repo (with the template) as suggested:
OP: Collection seems to be published (HTTP Code: 400, Message: Artifact already exists Code: invalid), but not accessible in the UI or via 'collection install' · Issue #3282 · ansible/galaxy · GitHub
I have published the initial version 1.0.0 of my SSH collection and my account does not show the collection under my namespace
Trying to publish the same version again:
❯ ansible-galaxy collection publish drew1kun-ssh-1.0.0.tar.gz Publishing collection artifact '/Users/drew/Library/CloudStorage/Dropbox/Code/github/ansible/ansible-collections/ansible-collection-ssh/drew1kun-ssh-1.0.0.tar.gz' to release_galaxy https://galaxy.ansible.com/api/ ERROR! Error when publishing collection to release_galaxy (https://galaxy.ansible.com/api/) (HTTP Code: 400, Message: Artifact already exists Code: invalid)
Trying to install the collection:
❯ ansible-galaxy collection install drew1kun.ssh Starting galaxy collection install process Process install dependency map ERROR! Failed to resolve the requested dependencies map. Could not satisfy the following requirements: * drew1kun.ssh:* (direct request)
The collection is visible in the UI under my namespace (so I could delete it and reupload):
Other collections, that were published before Galaxy NG release are visible, but not the one I pushed tonight.
404 is returned despite the API returning (HTTP Code: 400, Message: Artifact already exists Code: invalid) when trying to publish the same version that has been pushed previously.