-
-
Notifications
You must be signed in to change notification settings - Fork 198
Feat/pgsodium vault updates #411
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
Merged
Merged
Conversation
This file contains hidden or 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
Can also confirm this works locally. I think the error is because the test is using an older build which already has I'll modify the PR a bit to make it idempotent |
sweatybridge
approved these changes
Dec 9, 2022
ea877ec
to
b5ff8c5
Compare
c875eb2
to
8c307a7
Compare
pcnc
approved these changes
Dec 9, 2022
hf
pushed a commit
that referenced
this pull request
Jan 23, 2023
* update release candidate ami for pgsodium and vault updates. * update pgsodium and vault. * update release candidate ami for pgsodium and vault updates. * remove vault ami release. * bump vault version. * add pgsodium in migration file, not at ami creation point. * spelled extension name wrong. * remove pgsodium from docker init, add as migration script. * make migration idempotent * bump version * fix schema check in tests * add vault schema to tests * fix extension dependencies after extension creation * bump vault Co-authored-by: Bobbie Soedirgo <[email protected]> Co-authored-by: Qiao Han <[email protected]>
damonrand
pushed a commit
to cepro/postgres
that referenced
this pull request
Jun 15, 2025
* update release candidate ami for pgsodium and vault updates. * update pgsodium and vault. * update release candidate ami for pgsodium and vault updates. * remove vault ami release. * bump vault version. * add pgsodium in migration file, not at ami creation point. * spelled extension name wrong. * remove pgsodium from docker init, add as migration script. * make migration idempotent * bump version * fix schema check in tests * add vault schema to tests * fix extension dependencies after extension creation * bump vault Co-authored-by: Bobbie Soedirgo <[email protected]> Co-authored-by: Qiao Han <[email protected]>
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 kind of change does this PR introduce?
updates to pgsodium and vault.