jcjveraa opened a new issue, #37928: URL: https://github.com/apache/superset/issues/37928
### Bug description When using [the release build of 6.0.0](https://hub.docker.com/r/apache/superset/tags?name=6.0.0), environmental parameters such as `SUPERSET_LOG_LEVEL` are completely ignored, as demonstrated by my post in this issue: https://github.com/apache/superset/issues/37842#issuecomment-3890688837. I see other issues related to variables being ignored e.g. #37924 & #37864 - perhaps this is some larger bug where something went wrong in loading environmental args? ### Screenshots/recordings Copy of what I posted in https://github.com/apache/superset/issues/37842#issuecomment-3890688837 ``` $ env | grep SUPERSET_LOG_LEVEL SUPERSET_LOG_LEVEL=DEBUG $ superset re-encrypt-secrets Loaded your LOCAL configuration at [/app/pythonpath/superset_config.py] 2026-02-12 12:30:19,865:INFO:alembic.runtime.migration:Context impl PostgresqlImpl. 2026-02-12 12:30:19,866:INFO:alembic.runtime.migration:Will assume transactional DDL. 2026-02-12 12:30:20,303:INFO:superset.app:Syncing configuration to database... 2026-02-12 12:30:20,317:INFO:superset.app:Configuration sync to database completed successfully 2026-02-12 12:30:21,330:INFO:superset.utils.encrypt:Collecting info for re encryption 2026-02-12 12:30:21,331:INFO:superset.utils.encrypt:All tables processed $ superset --debug re-encrypt-secrets Loaded your LOCAL configuration at [/app/pythonpath/superset_config.py] 2026-02-12 12:30:38,176:DEBUG:superset.utils.logging_configurator:logging was configured successfully 2026-02-12 12:30:38,234:DEBUG:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'> 2026-02-12 12:30:38,251:DEBUG:superset.initialization:Setting database isolation level to READ COMMITTED 2026-02-12 12:30:39,049:INFO:alembic.runtime.migration:Context impl PostgresqlImpl. 2026-02-12 12:30:39,049:INFO:alembic.runtime.migration:Will assume transactional DDL. 2026-02-12 12:30:39,476:INFO:superset.app:Syncing configuration to database... 2026-02-12 12:30:39,484:DEBUG:superset.commands.theme.seed:Updated system theme: THEME_DEFAULT 2026-02-12 12:30:39,490:DEBUG:superset.commands.theme.seed:Updated system theme: THEME_DARK 2026-02-12 12:30:39,491:INFO:superset.app:Configuration sync to database completed successfully 2026-02-12 12:30:40,534:INFO:superset.utils.encrypt:Collecting info for re encryption 2026-02-12 12:30:40,535:INFO:superset.utils.encrypt:All tables processed $ ``` ### Superset version 6.0.0 ### Python version 3.10 ### Node version I don't know ### Browser Chrome ### Additional context _No response_ ### Checklist - [x] I have searched Superset docs and Slack and didn't find a solution to my problem. - [x] I have searched the GitHub issue tracker and didn't find a similar bug report. - [x] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section. -- 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]
