chore: metabase user and password for environments sync #108
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
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.
What
Added 2 new variables in backend/staging and backend/development environments to sync the databases with production
How
Adding in each environment the file secret-03_sealed.yaml
*Maintaining the history of changes with the others files
k8s/website/django/development
k8s/website/django/staging
Why
In order to the databases environments be sync with the databases production the command with cron and fetch_metabase in backend repository was created, but it only works with the credentials of metabase production, when the pods are reestarting they used to lost those two variables, and then they stopped working. Now that these two variables are inside de configured secrets for the environmets even if the pods reestart the sync still be working.