Some time ago I’ve started work on getting openvswitch.openvswitch collection working for recent Ansible versions (and generally picking up work on that ,abandoned’’ collection).
Time has come to do a release - I’ve created a GitHub release but Galaxy did not import the new version (see Ansible Galaxy and Release OpenvSwitch Ansible collection release 2.2.0 · ansible-collections/openvswitch.openvswitch · GitHub).
I don’t have any authority over the collection in Galaxy - what are the next steps I should do?
1 Like
I believe that repository is missing the galaxy token for the namespace among secrets.
So basically the question is - how are we getting the token to publish the new release to the galaxy?
Hi @mnasiadka
@noonedeadpunk is correct, you’ll need the namespace token to be able to publish the collection to Ansible Galaxy.
Are you the primary maintainer of this collection now, and is this your GitHub user? mnasiadka (Michał Nasiadka) · GitHub
EDIT: You’ll also need a GitHub Action Workflow to trigger the upload to Galaxy.
@dbrennand yes - me and @noonedeadpunk (noonedeadpunk (Dmitriy Rabotyagov) · GitHub) are now primary maintainers of this collection
Yup, we are aware of the github action, and that is the easy part so to say 
I see from a previous thread about you two both being maintainers for this collection: Unmaintained collection: openvswitch.openvswitch - #25 by noonedeadpunk
I’ve added both your GitHub users with the needed permissions to the openvswitch namespace on Galaxy 
This should unblock your release process. Also, whilst I was looking at the collection I noticed that the CHANGELOG.rst file is missing changelogs for 2.2.0.
And also galaxy.yml contains wrong version for the tag, yeah…
Thanks a lot for granting permissions! These issues will be addressed before the actual release:)
1 Like
That’s great! Thanks @noonedeadpunk. Looking forward to hearing about the release
If this is resolve on your side, appreciate if you could mark this as resolved.