You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "jack (JIRA)" <ji...@apache.org> on 2019/01/23 07:34:00 UTC

[jira] [Commented] (AIRFLOW-103) Allow jinja templates to be used in task params

    [ https://issues.apache.org/jira/browse/AIRFLOW-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749617#comment-16749617 ] 

jack commented on AIRFLOW-103:
------------------------------

Totally agree with [~colinbreame] this is very common use case for me as well.

Love to see this feature in.

> Allow jinja templates to be used in task params
> -----------------------------------------------
>
>                 Key: AIRFLOW-103
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-103
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: operators
>            Reporter: Paul Rhodes
>            Priority: Minor
>
> At present when defining an Operator it isn't possible to reference template variables such as {{ds}} in the params block.
> Enabling this makes it easier to reuse Operators with very similar configurations. An example of this might be a BashOperator which runs a large (possibly external) script that only has a couple of configuration changes used between different runs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)