feat: Extend enable/disable/set-state to all feature view types and REST APIs by rpathade · Pull Request #6431 · feast-dev/feast
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Conversation
What this PR does / why we need it:
Extends the feature view state management (introduced in #6401) to all feature view types and adds REST API support:
- Adds
enable,disable,set-stateCLI commands underon-demand-feature-viewsandstream-feature-views - Updates
describefor on-demand and stream feature views to showenabledandstate - Adds REST API endpoints:
PUT /feature_views/{name}/enable,/disable,/set-state - Adds
type: ignoreannotations for mypy sinceBaseFeatureViewlacksenabled/stateattributes
Which issue(s) this PR fixes:
Fixes #6429
Checks
- I've made sure the tests are passing.
- My commits are signed off (
git commit -s) - My PR title follows conventional commits format
Testing Strategy
- Unit tests
- Integration tests
- Manual tests
- Testing is not required for this change
Misc
rpathade
changed the title
Feat/extend state management cli api
feat: Extend enable/disable/set-state to all feature view types and REST APIs
rpathade
changed the title
feat: Extend enable/disable/set-state to all feature view types and REST APIs
feat: Extend enable/disable/set-state to all feature view types and REST APIs
rpathade
marked this pull request as ready for review
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