You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I noticed that Ansible Galaxy lists 1.1.0 as the latest version, while 1.2.0 is the latest on GitHub. Could you please push 1.2.0 to the Ansible Galaxy?
The text was updated successfully, but these errors were encountered:
Unfortunately i cannot do that, since some time ago Galaxy disabled logins through anything but GitHub and they require granting access to all metadata related to Organisations attached to my primary GitHub account, which I cannot allow myself for security reasons. There's also no legitimate technical reason why Galaxy should require Organisation data access for role uploads.
Yes, but as I'm not actively using Ansible anymore (I switched to Nix), managing a separate account on github just for it is not too appealing to me. I don't mind if you publish the role under your name, and you could automate upstream updates of your fork if you don't want to cut the ties with the main repository.
It also doesn't mean that I am abandoning the repository, it's just I don't find Galaxy with its recent changes to authentication very appealing. There are other means how Ansible roles could be delivered to your infrastructure repository, without compromising on precision and safety features.
Hello, I noticed that Ansible Galaxy lists 1.1.0 as the latest version, while 1.2.0 is the latest on GitHub. Could you please push 1.2.0 to the Ansible Galaxy?
The text was updated successfully, but these errors were encountered: