-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🌱 api: deprecate FailureMessage and FailureReason #11317
🌱 api: deprecate FailureMessage and FailureReason #11317
Conversation
9331dcc
to
124f481
Compare
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.
One nit.
I've added an additional sub-task in the proposal for the other fields. But they are more complex and might require more discussion. So I think it makes sense to only deprecate failureReason & failureMessage in this PR and handle the other fields in follow-up PR(s)
124f481
to
9a7d894
Compare
/lgtm |
LGTM label has been added. Git tree hash: 8147135ba36b206a859c9752f06702653e778c06
|
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer 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:
Deprecates
.status.failureMessage
and.status.failureReason
as proposed in docs/proposals/20240916-improve-status-in-CAPI-resources.md.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 #11105
/area api