potiuk opened a new issue, #59860: URL: https://github.com/apache/airflow/issues/59860
### Body Currently the `expose config` allows deployment manager to expose also sensitive data - when set to True https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html#expose-config. The `non-sensitive-only` value causes sensitive field masking. With the discussion mentioned in #59838 we agreed that we should **never** expose sensitive data over any public API where UI user can authenticate (only via task-sdk API where tasks get dedicated JWT token) This means that: * Only `True/False` should be expected for expose-config and `True` means that sensitive fields are masked * We should add fallback - when "non-sensitive-data" is set for the parameter it should be treated as `True` and deprecation warning should be raised * newsfragment should be added explaining the behaviour change ### Committer - [x] I acknowledge that I am a maintainer/committer of the Apache Airflow project. -- 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]
