kaxil commented on a change in pull request #17007:
URL: https://github.com/apache/airflow/pull/17007#discussion_r669963621



##########
File path: docs/apache-airflow/security/secrets/mask-sensitive-values.rst
##########
@@ -0,0 +1,79 @@
+ .. Licensed to the Apache Software Foundation (ASF) under one
+    or more contributor license agreements.  See the NOTICE file
+    distributed with this work for additional information
+    regarding copyright ownership.  The ASF licenses this file
+    to you under the Apache License, Version 2.0 (the
+    "License"); you may not use this file except in compliance
+    with the License.  You may obtain a copy of the License at
+
+ ..   http://www.apache.org/licenses/LICENSE-2.0
+
+ .. Unless required by applicable law or agreed to in writing,
+    software distributed under the License is distributed on an
+    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+    KIND, either express or implied.  See the License for the
+    specific language governing permissions and limitations
+    under the License.
+
+.. _security:mask-sensitive-values:
+
+Masking sensitive data
+----------------------
+
+Airflow will by default mask Connection passwords and sensitive Variables and 
keys from a Connection's
+extra (JSON) field when they appear in Task logs, in the Variable and in the 
Rendered fields views of the UI.
+
+It does this by looking for the specific *value* appearing anywhere in your 
output. This means that if you
+have a connection with a password of ``a``, then every instance of the letter 
a in your logs will be replaced
+with ``***``.
+
+To disable masking you can setting 
:ref:`config:core__hide_sensitive_var_conn_fields` to false.

Review comment:
       ```suggestion
   To disable masking you can set 
:ref:`config:core__hide_sensitive_var_conn_fields` to false.
   ```




-- 
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