-
Notifications
You must be signed in to change notification settings - Fork 1.4k
📖 Align v1beta2 contract to API conventions around optional fields #12418
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
📖 Align v1beta2 contract to API conventions around optional fields #12418
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Q: should we surface in the migration doc at least the rules that are changed
0f89bf1
to
50e230a
Compare
I think I got all of them now. All others should be new fields |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
I will make another pass on contract at the end, may be we should also add a note about validation but we will see
LGTM label has been added. Git tree hash: 702aadf7d4e0bb93b4cdf3200a0638c44b398e39
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Part of #10852