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
It'd be really useful if we could allow users to run a component from a different repository by using the dependency/repository sugar syntax. Something like:
viash run github://openpipelines-bio/openpipeline:0.3.0:mynamespace/mycomponent
The exact syntax be discussed, of course. Maybe something simpler might be:
viash run mynamespace/mycomponent --repository github://openpipelines-bio/openpipeline:0.3.0
This would allow something like this:
viash run mynamespace/mycomponent --repository local
to also work, which would run but not build a component from the current project.
Why is this feature beneficial?
Being able to run a component from a different repository would be useful but is not always trivial, since a component can have resources.
Alternatives considered
No response
Possible solution
No response
Confirmation
I have searched the existing issues to make sure this is not a duplicate request.
I have provided clear and concise information about the feature.
The text was updated successfully, but these errors were encountered:
Feature summary
Support dependency sugar syntax during viash run
Feature description
It'd be really useful if we could allow users to run a component from a different repository by using the dependency/repository sugar syntax. Something like:
The exact syntax be discussed, of course. Maybe something simpler might be:
This would allow something like this:
viash run mynamespace/mycomponent --repository local
to also work, which would run but not build a component from the current project.
Why is this feature beneficial?
Being able to run a component from a different repository would be useful but is not always trivial, since a component can have resources.
Alternatives considered
No response
Possible solution
No response
Confirmation
The text was updated successfully, but these errors were encountered: