Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Automate detection of existing Supabase Postgres secret #443

Closed
CollectiveUnicorn opened this issue Apr 25, 2024 · 2 comments
Closed

Automate detection of existing Supabase Postgres secret #443

CollectiveUnicorn opened this issue Apr 25, 2024 · 2 comments
Labels
blocked 🛑 Something needs to happen before this issues is worked tech-debt Not a feature, but still necessary

Comments

@CollectiveUnicorn
Copy link
Contributor

Describe what should be investigated or refactored

As a LeapfrogAI dev, I would like an automatic way to determine when the variable EXISTING_POSTGRES_SECRET needs to be set without human intervention on Zarf deployment. Currently the first time Supabase is deployed this variable needs to be set to an empty string and the second time then it needs to be supabase-postgresql-backup to prevent the secret key from being lost.
@CollectiveUnicorn CollectiveUnicorn added tech-debt Not a feature, but still necessary blocked 🛑 Something needs to happen before this issues is worked labels Apr 25, 2024
@CollectiveUnicorn
Copy link
Contributor Author

Blocked by #345

@CollectiveUnicorn
Copy link
Contributor Author

Resolved as a part of #345 by selectively adding helm.sh/resource-policy: keep to the randomly generated resource.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
blocked 🛑 Something needs to happen before this issues is worked tech-debt Not a feature, but still necessary
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@CollectiveUnicorn