use external secrets for pgvector secret#80
Merged
dminnear-rh merged 1 commit intoJun 4, 2026
Merged
Conversation
dminnear-rh
force-pushed
the
add-pgvector-credentials-to-secrets
branch
8 times, most recently
from
e8268d5 to
cb92415
Compare
dminnear-rh
force-pushed
the
add-pgvector-credentials-to-secrets
branch
from
cb92415 to
088217a
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
@sauagarwa @trujillm
Updates the pgvector chart to use secrets provided by the VP framework. This will work on the demo env as-is since a password for pgvector is autogenerated if not provided.
Also, made some small tweaks to the README to reflect the current state of this pattern.