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

Posted to commits@airflow.apache.org by "Chris Riccomini (JIRA)" <ji...@apache.org> on 2016/06/21 17:30:58 UTC

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

     [ https://issues.apache.org/jira/browse/AIRFLOW-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Riccomini closed AIRFLOW-162.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: Airflow 1.8

> 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
>             Fix For: Airflow 1.8
>
>
> 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)