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

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

Commit bffc0c9ceccbd201094cbe129b4731c87d20286a in airflow's branch 
refs/heads/master from Qingping Hou
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=bffc0c9 ]

[AIRFLOW-4316] support setting kubernetes_environment_variables config section 
from env var (#5668)

When AIRFLOW_KUBERNETES_ENVIRONMENT_VARIABLES__AIRFLOW_HOME is set in
the scheduler, AIRFLOW_HOME should be set for workers, not airflow_home.

> Keys/Variable names in the 'kubernetes_environment_variables' section are 
> transformed to lower case
> ---------------------------------------------------------------------------------------------------
>
>                 Key: AIRFLOW-4316
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-4316
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: configuration, contrib
>    Affects Versions: 1.10.3
>            Reporter: Vlad Precup
>            Assignee: QP Hou
>            Priority: Major
>              Labels: configuration, kubernetes
>             Fix For: 2.0.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> All the environment variable names declared under the 
> kubernetes_environment_variables section are converted to lowercase in the 
> newly generated pods when running Airflow with the KubernetesExecutor in 
> version 1.10.3.
> The behavior is not aligned with the comments in the documentation / code 
> comments in the default config file, airflow.cfg.
> Investigation helper:
> Since we are treating all the sections uniformly in the configuration 
> component, all the keys are lowered (i.e. `configuration.py`, line 342 ->`key 
> = env_var.replace(section_prefix, '').lower()`)
> Please also write (a) unit test(s) for this special case.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to