Details
-
New Feature
-
Status: Resolved
-
P3
-
Resolution: Fixed
-
None
-
None
Description
Goal: Enable users to run pipelines from templates filled via CL (pipeline options)
Background: Currently, the Runner creates the JSON pipeline description which can be sent to the worker as is, since everything is already defined there (with links to gs:// for input and binaries). With the parametrized approach, those descriptions are empty and filled by the user or defaulted, so the pipeline needs to be stored somewhere first until the values become available.
Tasks:
1- Create template-style pipeline description (TemplateRunner)
The graph description is now a template (some parts are not filled) that needs to be saved.
2- Define values to inject to the template (ValueProviders API)
The placeholders can be filled with default values (static) or with dynamic key/value pairs provided at runtime (dynamic)
