GitHub user debggr added a comment to the discussion: Refusing to start due to insecure SECRET_KEY
@ineu Can you elaborate on how went about changing the password in DB? I'm stuck in a similar situation, were I'm providing the new secrets through `configOverrides` in values.yaml and see those new values being present in the superset_config.py, but the pod refuse to start throwing the same SECRET_KEY error. GitHub link: https://github.com/apache/superset/discussions/23598#discussioncomment-13927277 ---- This is an automatically sent email for notifications@superset.apache.org. To unsubscribe, please send an email to: notifications-unsubscr...@superset.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
