[
https://issues.apache.org/jira/browse/AIRFLOW-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ash Berlin-Taylor updated AIRFLOW-3178:
---------------------------------------
Description:
ConfigParser uses %-signs for interpolation, so if you need a literal % in
airflow.cfg it needs to be escaped in by specifying them as {{%%}}), but by
the time they are written out to the temporary config that is passed to
`airflow run` they escaping is lost.
This is also true for configuration via environment variables, where {{%}}
doesn't need to be escaped at all, but is included (sometimes needlessly) in
the config un-escaped.
was:
Even if percent sings are correctly escaped in the airflow.cfg (by specifying
them as {{%%}}) by the time they are written out to the temporary config that
is passed to `airflow run` they escaping is lost.
This is also true for configuration via environment variables, where {{%}}
doesn't need to be escaped at all, but is included (sometimes needlessly) in
the config un-escaped.
> `airflow run` config doens't cope with % in config values.
> ----------------------------------------------------------
>
> Key: AIRFLOW-3178
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3178
> Project: Apache Airflow
> Issue Type: Bug
> Reporter: Ash Berlin-Taylor
> Priority: Major
> Fix For: 1.10.1
>
>
> ConfigParser uses %-signs for interpolation, so if you need a literal % in
> airflow.cfg it needs to be escaped in by specifying them as {{%%}}), but by
> the time they are written out to the temporary config that is passed to
> `airflow run` they escaping is lost.
> This is also true for configuration via environment variables, where {{%}}
> doesn't need to be escaped at all, but is included (sometimes needlessly) in
> the config un-escaped.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
