| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Hi team! 👋 This adds the feast projects delete CLI command requested in #5095. The implementation directly calls store._registry.delete_project() since the abstract method is already fully implemented in all concrete registries (SQL, file, GCS, etc.) — there just wasn't a CLI surface for it yet. A few design choices I'd love feedback on:
Would appreciate a review when you get a chance! Happy to adjust based on feedback. 🙏 |
Sorry, something went wrong.
|
Thanks for the thorough review, @devin-ai-integration! Fix applied in the latest commit:
|
Sorry, something went wrong.
|
Hi team! 👋 Friendly ping on this PR adding feast projects delete CLI command. Happy to address any feedback! |
Sorry, something went wrong.
|
Hi team! 👋 Friendly ping on this PR adding feast projects delete CLI command (issue #5095). Happy to address any feedback! |
Sorry, something went wrong.
|
@mailtoboggavarapu-coder please fix the linting pr checks |
Sorry, something went wrong.
|
Hi team! Checking in on this PR adding the feast projects delete CLI command. The branch has been updated with the latest from master. Let me know if you'd like any changes! |
Sorry, something went wrong.
Exposes project deletion via the CLI. The new `feast projects delete <name>` command calls `store._registry.delete_project()` which is already implemented in all concrete registries. Adds an interactive confirmation prompt that can be bypassed with --yes/-y for scripted workflows. - Adds type guard (`assert store._registry is not None`) for mypy. - Catches both FeastObjectNotFoundException and ProjectNotFoundException so the CLI exits cleanly (exit code 1) for either variant raised by concrete registry implementations. Squashed history: this commit consolidates the previous unsigned commits on the branch into a single DCO-signed commit, per DCO requirements. Signed-off-by: Venkateswarlu Boggavarapu <mailtoboggavarapu@gmail.com>
|
Hi @ntkathole — thanks for the nudge! The PR checks have now been addressed:
Ready for another look whenever you have time — thanks again! |
Sorry, something went wrong.
…t_delete store._registry is always None until accessed via the lazy-init registry property. Using store._registry directly caused project_delete to always crash with an AssertionError. Fixes: Devin Review finding in feast-dev#6302 Signed-off-by: Venkateswarlu Boggavarapu <mailtoboggavarapu@gmail.com>
|
Thanks for the Devin review! Fixed the store._registry crash in the latest commit:
The registry property in feature_store.py handles initialization on first access, so this now works correctly. |
Sorry, something went wrong.
|
Closing this PR in favour of #6318 which has a clean single-commit history with a properly matched DCO sign-off (author name = Signed-off-by name). The DCO check was failing here because one commit had mailtoboggavarapu-coder as the git author name while the Signed-off-by said Venkateswarlu Boggavarapu. PR #6318 fixes this with a fresh single commit. All the same changes are included. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Summary
Closes #5095
Exposes project deletion through the CLI by adding a new feast projects delete <name> subcommand to the existing projects group.
What's changed
Added project_delete command to sdk/python/feast/cli/projects.py:
Design notes
Example
Checklist