-
Notifications
You must be signed in to change notification settings - Fork 14
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
ansible galaxy role listing out of date #31
Comments
There is an additional publishing step that is necessary to ask Galaxy to re-import the role. Since the repository changed, it does not look like I can ask Galaxy to re-import things. Looking at the UI and docs for Galaxy, I have not found a way to transfer the role in the same way we did with the GitHub repository. The best solution may be to re-publish this role to Galaxy under a new namespace. |
I had a peek too - did you see https://galaxy.ansible.com/docs/contributing/namespaces.html#adding-github-organizations-to-a-namespace ? That looks promising. |
I did not see it initially, but in messing with it now, it doesn't appear to let you drill down to the individual role level. I can only add/remove contributors for each namespaces, and activate/deactivate namespaces. |
Hmm. @lox @keithpitt might you be up for creating a new buildkite ansible galaxy namespace for this then inviting us to it? |
How would we do that @petemounce? |
Any update on the plans for this? Looks like it was pulled down from the site. |
@hectcastro I noticed that https://galaxy.ansible.com/azavea/buildkite-agent looks like it was last published a year ago, but we've been releasing since then.
Is there some kind of role transfer or permissions change that can take place? I'm unfamiliar with the galaxy site.
Versions of relevant software used
What happened
What you expected to happen
How to reproduce it (as minimally and precisely as possible):
Full logs to relevant components
Anything else we need to know
The text was updated successfully, but these errors were encountered: