Regenerate go

[zhilingc]

Update generated go protos.

[zhilingc]

/assign pradithya
/assign willem

[feast-ci-bot]

@zhilingc: GitHub didn't allow me to assign the following users: willem.

Note that only gojek members and repo collaborators can be assigned.
For more information please see the contributor guide

Details

In response to this:

/assign pradithya
/assign willem

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[pradithya]

/lgtm

[zhilingc]

/approve

[feast-ci-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: zhilingc

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [zhilingc]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[tims]

Can we automate this in the build? We should never have to remember this

[tims]

Eg for Go, we could make it regenerate the code and if it differs the merge should be aborted because of uncommitted changes

Python gen code should not be committed, it should be generated before we package wheels

[woop]

Eg for Go, we could make it regenerate the code and if it differs the merge should be aborted because of uncommitted changes

Python gen code should not be committed, it should be generated before we package wheels

Does this require an issue in itself?