You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "George Miller (JIRA)" <ji...@apache.org> on 2019/07/27 00:50:00 UTC
[jira] [Closed] (AIRFLOW-4850) Config _cmd options should
interpolate environment variables
[ https://issues.apache.org/jira/browse/AIRFLOW-4850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
George Miller closed AIRFLOW-4850.
----------------------------------
Resolution: Not A Problem
This workaround will work
|{{sql_alchemy_conn_cmd = bash -c 'echo ${POSTGRES_HOST}:${POSTGRES_PASSWORD}@postgres.com'}}|
> Config _cmd options should interpolate environment variables
> ------------------------------------------------------------
>
> Key: AIRFLOW-4850
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4850
> Project: Apache Airflow
> Issue Type: New Feature
> Components: configuration
> Affects Versions: 1.10.4
> Reporter: George Miller
> Assignee: George Miller
> Priority: Major
> Labels: pull-request-available
>
> When specifying a configuration like sql_alchemy_conn_cmd, it should be able to interpolate environment variables from the environment that airflow is running from. This is really useful when you mount secrets as environment variables and want to use them in this type of configuration option. For example, this currently does not work:
>
> `sql_alchemy_conn_cmd = echo ${POSTGRES_HOST}:${[POSTGRES_PASSWORD}@postgres.com|mailto:POSTGRES_PASSWORD%7D@postgres.com]`
>
> The change is really simple, and I opened a PR for it. [https://github.com/apache/airflow/pull/5479]
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)