You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "potiuk (via GitHub)" <gi...@apache.org> on 2023/03/12 20:12:09 UTC

[GitHub] [airflow] potiuk commented on issue #30039: Sensitive variable not masked in task logs when containing URL encoded string

potiuk commented on issue #30039:
URL: https://github.com/apache/airflow/issues/30039#issuecomment-1465288940

   No. How would you want to do it ? You would have to not only return the value but also remember that it was  retrieved from. A sensitively named variable.  Once you retrieve it, it looses the 'source association'. 
   
   You would have to always send the variable together with some metadata that would tell the provenience of the string and that would have to be implemented at the level of your code to verify the metadata before printing.
   
   There is no 'transparent' way where it can be handled - the best we can do is when this is a code which w can check with JiNJa before it gets Interpreted. 
   
   Probably it could be done using some super arcane methods (with a lot of performance overhead - where you would store retrieved variables and metadata about them but that would be terribly slow and complex and like it would not be possible to catch all usages of such retrieved value.
   
   But if you would like to attempt to make such an exercise - feel free to open PR :)


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org