-
Notifications
You must be signed in to change notification settings - Fork 165
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
Update Ansible-Galaxy #90
Comments
hmm I think I need more perms to import via galaxy.... even tho org has permission |
getting feedback from ansible-community team in irc.. |
so the irony is, that honestly these hashicorp roles don't belong under Ansible-community at all, as roles not the general scope of the Ansible-community org of repos. You'll see that it's mostly python-based tools to use with ansible. anyway they're not really interested in publishing roles at all... We could publish via collection and use the roles as submodules.......... or move these roles to a new org. |
Sorry, there was a lot to parse from this message. So is the plan to move this role to a collection? Or is it to move the role to a new org? |
Problem is need a plan... I'd like to be in sync with the other HashiCorp roles here... @ansible-community/hashicorp-tools do you all remember where we left off on this? |
I transferred the roles here because Brian didn't want to maintain them anymore. I am an (unpaid) Hashicorp Ambassador as well as an (unpaid) Ansible Ambassador, therefore I could 'transfer ownership' (keeping all the issues with the repo). I have no such power here (to transfer ownership). |
Need to transition ansible-galaxy entry to new repo location
The text was updated successfully, but these errors were encountered: