docs(contributing): How create or change SECRET_KEY #23420
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Explained how to change/create secret key.
docs(contributing): How create or change SECRET_KEY
|
Hi @nytai Just have a look. Let me know if docs are not perfect. |
nytai
approved these changes
Mar 23, 2023
mistercrunch
added
🏷️ bot
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Explained how to change/create secret key.
SUMMARY
When you are running an instance of superset naturally you might have added many DataBase connections, created a lot of charts and dashboards.
Suddenly if you want to change the SECRET_KEY to make your data encrypted , you need current secret key that has already encrypted your data.
Then you need to create a new SECRET_KEY
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
BEFORE SCREENSHOT
AFTER SCREENSHOT
ADDITIONAL INFORMATION
To change the SECRET_KEY we need to provide current secret key as PREVIOUS_SECRET_KEY in superset_config.py and New secret key should be assigned to SECRET_KEY variable.