[jira] [Commented] (AIRFLOW-162) Allow variables to be exposed in the templates

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on AIRFLOW-162:
---------------------------------------------------------

Commit 54f1c11b6f46b16bc41c289bab1738fec8ab9608 in incubator-airflow's branch refs/heads/master from [~alexvanboxel]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=54f1c11 ]

[AIRFLOW-162] Allow variable to be accessible into templates

Closes #1540 from alexvanboxel/AIRFLOW-162

AIRFLOW-162 Allow variable to be accessible into templates


> Allow variables to be exposed in the templates
> ----------------------------------------------
>
>                 Key: AIRFLOW-162
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-162
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: core
>            Reporter: Alex Van Boxel
>            Assignee: Alex Van Boxel
>            Priority: Trivial
>
> Allow variables to be exposed in the templates. This makes it possible to access them in the following way, example:
> {var.gcp_dataflow_base}/test-pipleline.jar
> In this example the basepath in configured in variables. This makes it possible to make some parts configurable (example for differences in prod/staging/test).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)