You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
.registry.path in feature_store.yaml is not updated based on interactive config during feast init #5388
After executing the command feast init -t postgres feature_repo and providing configuration interactively, the .registry.path in feature_repo/feature_repo/feature_store.yaml should be automatically populated based on the entered Postgres settings.
Current Behavior
The .registry.path in feature_repo/feature_repo/feature_store.yaml is not updated and remains the default value: postgresql://postgres:[email protected]:55001/feast.
2. Run feast init -t postgres feature_repo and fill out the configuration interactively
$ feast init -t postgres feature_repo
Postgres host [localhost]: test.example.com
Postgres port [5432]: 5432
Postgres DB name [postgres]: postgres
Postgres schema [public]: public
Postgres user: postgres
Postgres password:
Should I upload example data to Postgres (overwriting "feast_driver_hourly_stats" table)? [Y/n]: n
Creating a new Feast repository in /home/jovyan/feature_repo.
3. Check feature_store.yaml
Note that .registry.path still points to the default value and is not updated to match the entered host and database:
Activity
antznette1 commentedon Dec 17, 2025
I'd love to jump on this and create a PR for it.