[airflow] branch master updated: Allow using _CMD / _SECRET to set `[webserver] secret_key` config (#12742)

[ka...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

kaxilnaik pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/airflow.git


The following commit(s) were added to refs/heads/master by this push:
     new 0400ee3  Allow using _CMD / _SECRET to set `[webserver] secret_key` config (#12742)
0400ee3 is described below

commit 0400ee32d43c2544180fc7ac73ab42964a0dbd20
Author: Kaxil Naik <ka...@gmail.com>
AuthorDate: Wed Dec 2 14:39:26 2020 +0000

    Allow using _CMD / _SECRET to set `[webserver] secret_key` config (#12742)
    
    `[webserver] secret_key` is also a secret like Fernet key. Allowing
    it to be set via _CMD or _SECRET allows users to use the external secret store for it.
---
 airflow/configuration.py                 | 1 +
 docs/apache-airflow/howto/set-config.rst | 1 +
 2 files changed, 2 insertions(+)

diff --git a/airflow/configuration.py b/airflow/configuration.py
index d7dbb35..27724cd 100644
--- a/airflow/configuration.py
+++ b/airflow/configuration.py
@@ -130,6 +130,7 @@ class AirflowConfigParser(ConfigParser):  # pylint: disable=too-many-ancestors
         ('atlas', 'password'),
         ('smtp', 'smtp_password'),
         ('kubernetes', 'git_password'),
+        ('webserver', 'secret_key'),
     }
 
     # A mapping of (new option -> old option). where option is a tuple of section name and key.
diff --git a/docs/apache-airflow/howto/set-config.rst b/docs/apache-airflow/howto/set-config.rst
index 3ba7d9f..9e1bbc7 100644
--- a/docs/apache-airflow/howto/set-config.rst
+++ b/docs/apache-airflow/howto/set-config.rst
@@ -70,6 +70,7 @@ The following config options support this ``_cmd`` and ``_secret`` version:
 * ``password`` in ``[atlas]`` section
 * ``smtp_password`` in ``[smtp]`` section
 * ``git_password`` in ``[kubernetes]`` section
+* ``secret_key`` in ``[webserver]`` section
 
 The ``_cmd`` config options can also be set using a corresponding environment variable
 the same way the usual config options can. For example: