ashb opened a new pull request #18772:
URL: https://github.com/apache/airflow/pull/18772


   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.
   
   Note: this commit originally appears in 2019 (#4050) but a critical piece 
was missing, meaning that the secrets/envs were still actually appearing.
   
   Closes #18723
   
   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   
   ---
   **^ Add meaningful description above**
   
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code change, Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in 
[UPDATING.md](https://github.com/apache/airflow/blob/main/UPDATING.md).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to