-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add Ansible-Galaxy release workflow #6
Conversation
I think the release through the CI will create a new |
Should we not create a new one, with the proper name - called |
I mean from our side we don't want this at all, it'll be part of the main role and gravity's job to install and manage, making some of these older individual roles (also tusd) less useful. |
re the name, I don't think that's what will happen. the name is taken from the meta. |
Oh, yeah! Thank you! |
This assumes you have tusd on the headnode, or need gravity on an external node to manage tusd? |
Yes. (Though I suspect, @natefoo can confirm) it will look a lot like headnode: run ansible-galaxy, install galaxy |
ping @bgruening, @mira-miracoli |
Eventually this will be folded into the collection but it's fine continuing as its own thing for now. I don't want to add anything else to the monolithic ansible-galaxy role. |
No description provided.