Open
Description
Is your feature request related to a problem? Please describe.
We should be able to run a pipelines provided from a plugin with different configurations/scopes without editing the project file between runs.
Describe the solution you'd like
Provide a way to define different run configurations for the same plugin provided pipeline.
Describe alternatives you've considered
Instead of providing a new scope for a plugin, we should be able to define a pipeline in a current scope. We could provide a module path to be loaded into the scope and use the scope configurations to provide !config values and targets etc.
Additional context
Path could be scheme based and could support file://
package://
...
Metadata
Assignees
Type
Projects
Status
No status