-
Notifications
You must be signed in to change notification settings - Fork 180
attempt to patchStatus regardless of finalizer #64
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
attempt to patchStatus regardless of finalizer #64
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.
Please see aws-controllers-k8s/community#931. We will need to figure out a different solution to this, because this conditional check on whether the resource is under management was specifically added in to prevent the issue described in 931.
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.
femto-nit inline, otherwise I'm good with this!
fad0a55 to
9e97f84
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.
👍
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jaypipes, vijtrip2 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 |
Description of changes:
Managedbefore performing theCREATEcallREAD_ONEcall which precedesCREATEcallStatus.Conditionindicating reference resolution failedNotFounderror while status patching of deleted resource is caught and not logged in controller logsBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.