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

Support a smoother transition from hyphens to underscores in role names #1128

oneswig opened this Issue Sep 4, 2018 · 0 comments


None yet
2 participants

oneswig commented Sep 4, 2018

Feature Request

The Galaxy role server can internally migrate to underscores in role names, but should serve roles for client requests using either hyphens or underscores.

Use Case

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.

Proposed Solution

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:

  • At the most basic level this may be solvable through URL rewrite rules.
  • If a static document tree is in use, it could be populated at both locations.
  • For dynamic-generated content, a solution within Galaxy's server code should equally be possible.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment