ASchmidtGit opened a new issue, #24201:
URL: https://github.com/apache/superset/issues/24201

   Hey, we want to update from 1.5.0 to 2.1.0 and did not change our secret key 
in older deployments.
   
   I generated a key with "openssl rand -base64 42" and received the previous 
key with:
   ```
   superset shell
   from flask import current_app; print(current_app.config["SECRET_KEY"])
   ```
   
   Then i changed my superset_config.py to include the following:
   
   PREVIOUS_SECRET_KEY = "CHANGE_ME_TO_A_COMPLEX_RANDOM_SECRET"   
   SECRET_KEY = "MYGENERATEDKEY"
   
   and mounted my Pythonpath: "/app/pythonpath:app/docker/pythonpath_dev" which 
includes the superset_config.py.
   
   But i still get the following error:
   ```
   
--------------------------------------------------------------------------------
                                       WARNING
   
--------------------------------------------------------------------------------
   A Default SECRET_KEY was detected, please use superset_config.py to override 
it.
   Use a strong complex alphanumeric string and use a tool to help you generate 
   a sufficiently random sequence, ex: openssl rand -base64 42
   
--------------------------------------------------------------------------------
   
--------------------------------------------------------------------------------
   Refusing to start due to insecure SECRET_KEY
   [2023-05-24 15:05:11 +0000] [215] [INFO] Worker exiting (pid: 215)
   Loaded your LOCAL configuration at [/app/pythonpath/superset_config.py]
   [2023-05-24 15:05:11 +0000] [222] [INFO] Booting worker with pid: 222
   ```
   
   Using "superset re-encrypt-secrets" does not work either and just returns 
the same warning. (i ran this command in the Superset webb app container)
   
   Did i miss something?


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to