-
Notifications
You must be signed in to change notification settings - Fork 0
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
fix galaxy URL #1
Comments
Thanks for report, readme updated 1ebe823 |
You should also add the master branch again, or change the URL galaxy uses. Otherwise one will not get the newest version in case of new ones and you need to keep the 1.0 branch |
may be when ansible galaxy start to use semver |
More details here ansible/galaxy-issues#70. Please upvote galaxy issue :) |
I think you are mistaken me here. As an ArchLinux User I am used to just install the newest version, following this I don't want to explicitly specify a version. So it would be nice to have a working standard URL again. |
Fyi, there's another galaxy bug here. It always takes "master" as the default branch (when no version specified), although the repo has - for instance in our situation - "2.0" |
The download URL in the galaxy role points to the master branch archive. As you've deleted this branch, you get a 404 trying to download the role using ansible-galaxy cli
Workaround is to add a version parameter in requirements.yml
The text was updated successfully, but these errors were encountered: