Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
Support a smoother transition from hyphens to underscores in role names #1128
The Galaxy role server can internally migrate to underscores in role names, but should serve roles for client requests using either hyphens or underscores.
In the transition to Galaxy 3.0, a change in naming was introduced that led to the renaming of all our roles from using hyphens to underscores. Without apparent warning this led to all our deploys and CI breaking.
This disruption to us, our clients and the user base of our roles could be avoided if the original name of the role was still treated as valid.
These two URLs should translate to retrieve the same object, or be populated with duplicated content to have the same effect:
Break the world for Galaxy users?
Various options here:
Reiterating what was stated on #779:
As we move toward Mazer and changing the way Ansible content is installed to the local filesystem, path and content names are expected to be Python compatible. So for this reason, we will no longer support '-' in namespace, repository and content names.
For existing Galaxy users, we will continue to allow '-' in one-off cases by performing manual database updates on request. The goal is to not break existing content, and as best we can, help users transition to new names.
If you do run into a case where you need '_' converted to '-', please file an issue, and we'll perform the update as quickly as possible.