Francisco Arceo

You may have to force update your symlink if you're using brew.

Some things we'll have to do: ~~1. Handle purely `feature_views` i.e., `features="feature_view"`~~ 2. Handle feature references; i.e., `["feature_view:feature_1","feature_view:feature_2",...]` etc. 3. Handle [feature services ](https://docs.feast.dev/getting-started/concepts/feature-retrieval#feature-services) We'll have to serialize the data...

Whoops, nevermind that was based on outdated documentation I think.

@tokoko I'm confused about why we would do this? I think adding a client that makes the behavior intuitive makes sense but that's basically in the [Python feature server](https://github.com/feast-dev/feast/blob/ee51fbfe3f40e637084c5ecf51f7463b840d58b4/sdk/python/feast/feature_server.py#L24).

FYI @asg017 wanted to let you know I'm going to add this in Feast.

> I'm undecided between having `create, update, delete` vs a single `edit` action. @tokoko I would suggest each, as the flexibility will be great for users

I am also pro Option 2 at the moment

I have access to Dockerhub but not gcr

I'm not particularly familiar with the second scenario you outlined but I do agree that Feast should be a toolbox that could support both scenarios. That said, and given my...

Awesome! I'll review this in more detail later. Do you want to collaborate on the doc? Feel free to add your name and suggest some changes.