fix: Populate Postgres registry.path during feast init
#5785
+15
−1
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
Signed-off-by: antznette1 <ochiezeanthonette@gmail.com>
antznette1
changed the title
registry.path during feast initregistry.path during feast init
Signed-off-by: antznette1 <ochiezeanthonette@gmail.com>
Contributor
Author
|
Would appreciate a review when possible |
franciscojavierarceo
approved these changes
Dec 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
registry.pathto use the sameDB_*placeholders as the online/offline store config.Why
feast init -t postgresleavingregistry.pathat the default hardcoded URL. Fixes.registry.pathinfeature_store.yamlis not updated based on interactive config duringfeast init#5388.Testing