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
I'm currently working on using the RunPipelineJobOperator of airflow to trigger Vertex AI Pipelines (VAIP). One of the argument of this operator is the parameter_values that is a dict of str -> Any that is passed to the VAIP execution as parameters. As fair as I know, this field is not templatable (I cannot use Jinja templates on it).
What I'd like to do is pass airflow parameters, taking advantage of its UI, to allow the user triggering the airflow pipeline to specify the parameters that will be used by the vertex ai pipeline.
I do that by creating a custom operator that inherits from RunPipelineJobOperator and makes the argument templatable with jinja, but I think it's worth considering making it templatable from start.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi everyone!
I'm currently working on using the
RunPipelineJobOperator
of airflow to trigger Vertex AI Pipelines (VAIP). One of the argument of this operator is theparameter_values
that is a dict ofstr -> Any
that is passed to the VAIP execution as parameters. As fair as I know, this field is not templatable (I cannot use Jinja templates on it).What I'd like to do is pass airflow parameters, taking advantage of its UI, to allow the user triggering the airflow pipeline to specify the parameters that will be used by the vertex ai pipeline.
I do that by creating a custom operator that inherits from RunPipelineJobOperator and makes the argument templatable with jinja, but I think it's worth considering making it templatable from start.
Beta Was this translation helpful? Give feedback.
All reactions