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
{{ message }}
This repository has been archived by the owner on Jun 18, 2021. It is now read-only.
The dependencies of galaxy roles have the form openmicroscopy.basedeps, however the playbooks in this repository expect a role name without a prefix (just basedeps). As a result some roles are installed twice, with and without the prefix.
Proposed fix: all playbooks using Galaxy roles should use the prefix.
The text was updated successfully, but these errors were encountered:
What are the alternatives? e.g. using name: aggressively to not have duplicates?
That might work, but most galaxy roles/examples seem to use PREFIX. in playbooks.
will users want to overwrite with updating playbooks (i.e. swap to someuser.basedeps in requirements.yml`)
Do you mean always use the prefix in playbooks?
if we use openmicroscopy.basedeps everywhere, should we also prefix the variable names further?
Don't know, other galaxy roles that I've looked at don't, and chances are if you're running two roles with the same name in the same playbook you're asking for trouble.
That was in response to your comment about prefixing variables with the galaxy org. My proposal is to prefix the roles when they're d playbooks, but not the variables since I don't think you're likely to want to use two roles with the same name from different organisations.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The dependencies of galaxy roles have the form
openmicroscopy.basedeps
, however the playbooks in this repository expect a role name without a prefix (justbasedeps
). As a result some roles are installed twice, with and without the prefix.Proposed fix: all playbooks using Galaxy roles should use the prefix.
The text was updated successfully, but these errors were encountered: