-
-
Notifications
You must be signed in to change notification settings - Fork 205
feat: vault sans pgsodium #1431
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.
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
Conversation
6847543
to
086c825
Compare
@soedirgo it also looks like you need to actually deactivate pgsodium extension from psql bundle probably something like
Depending on exactly what you need to do here Also, you may need to revise the migrations, because:
|
We want to keep pgsodium available (for now), but automatically
This error still puzzles me - from the looks of it it happens on |
I fixed this error in my pr to this pr |
I’ll create a new pr against this branch to try and continue fixing the testdb issue |
b5126d4
to
b9ec53e
Compare
* chore: also deactivate supabase_vault in test * chore: check that refs are removed * chore: add a pattern for when vault at end of line * fix: yaml typo * chore: retry on fail for initial installs * chore: revert logic for ansible install
#1440) * chore: create a workflow_dispatch only method with input, for docker release * chore: move file to correct dir
b9ec53e
to
d7f6f7c
Compare
CI failures have been fixed (thanks Sam 🙏 ) ready to merge now |
Needs https://github.com/supabase/infrastructure/pull/20621 to be deployed first
Updates Vault to 0.3.1 which no longer requires pgsodium. Also omits pgsodium from the list of extensions that are automatically installed on new projects.
Tested logical backup & restore and pg_upgrade flows locally.