potiuk opened a new pull request #16424:
URL: https://github.com/apache/airflow/pull/16424


   Using Iterable in SecretsMasker might cause undesireable
   side effect in case the object passed as log parameter
   is an iterable object and actually iterating it is not idempotent.
   
   For example in case of botocore, it passes StreamingBody
   object to log and this object is Iterable. However it can be
   iterated only once. Masking causes the object to be iterated
   during logging and results in empty body when actual results
   are retrieved later.
   
   This change only iterates list type of objects and recurrently
   redacts only dicts/strs/tuples/sets/lists which should never
   produce any side effects as all those objects do not have side
   effects when they are accessed.
   
   Fixes: #16148
   
   <!--
   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.

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


Reply via email to