Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automated repo upgrades #2629

Closed
achals opened this issue Apr 29, 2022 · 1 comment
Closed

Automated repo upgrades #2629

achals opened this issue Apr 29, 2022 · 1 comment
Assignees
Labels
kind/feature New feature or request priority/p0 Highest priority

Comments

@achals
Copy link
Member

achals commented Apr 29, 2022

Is your feature request related to a problem? Please describe.
Feast feature repos are essentially declarative python code. When we make changes to the API used to declare Feast objects, we have to deprecate old fields, introduce new fields, and support both for multiple releases giving users a chance to upgrade their repos.

This pushes a lot of migration work on to users and is generally a non-scalable process.

Describe the solution you'd like

We should be able to automate trivial upgrades to the feature definitions (for things such as field renames or similar refactoring) automatically, in the same way as terraform.

There are tools like pybowler and fissix that allow for refactoring code.

We can integrate these into a feast upgrade command.

@achals achals added kind/feature New feature or request priority/p1 labels Apr 29, 2022
@achals achals self-assigned this Apr 29, 2022
@kevjumba
Copy link
Collaborator

kevjumba commented May 11, 2022

Found feast deprecations that should be automatically deprecated as per #2670
All of these should need upgrades and is more motivation to support feast upgrade
Screen Shot 2022-05-11 at 2 40 41 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request priority/p0 Highest priority
Projects
None yet
Development

No branches or pull requests

2 participants