[
https://issues.apache.org/jira/browse/AIRFLOW-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16852813#comment-16852813
]
ASF subversion and git services commented on AIRFLOW-4448:
----------------------------------------------------------
Commit 85a93b6551a7cfad4f0fd287beec264aca93a6d0 in airflow's branch
refs/heads/v1-10-stable from Ash Berlin-Taylor
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=85a93b6 ]
[AIRFLOW-4448] Don't bake ENV and _cmd into tmp config for non-sudo (#4050)
If we are running tasks via sudo then AIRFLOW__ config env vars won't be
visible anymore (without them showing up in `ps`) and we likely might
not have permission to run the _cmd's specified to find the passwords.
But if we are running as the same user then there is no need to "bake"
those options in to the temporary config file -- if the operator decided
they didn't want those values appearing in a config file on disk, then
lets do our best to respect that.
(cherry picked from commit 670f2ed52974038d4ee693674d3c18c015030b5f)
> Don't bake env vars/cmd in to tmp config when not using impersonation
> ---------------------------------------------------------------------
>
> Key: AIRFLOW-4448
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4448
> Project: Apache Airflow
> Issue Type: Bug
> Reporter: Ash Berlin-Taylor
> Priority: Major
> Fix For: 1.10.4
>
>
> If we are running tasks via sudo then AIRFLOW__ config env vars won't be
> visible anymore (without them showing up in {{ps}}) and we likely might
> not have permission to run the _cmd's specified to find the passwords.
> But if we are running as the same user then there is no need to "bake"
> those options in to the temporary config file -- if the operator decided
> they didn't want those values appearing in a config file on disk, then
> lets do our best to respect that.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
