fix: avoid returning resolved on error#219
fix: avoid returning resolved on error#219michaelhtm wants to merge 1 commit intoaws-controllers-k8s:mainfrom
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: michaelhtm The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@michaelhtm: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. I understand the commands that are listed here. |
Description of changes:
Using resolved as a return value may not always lead to desired results.
When ResolveReferences is called for resources that don't reference any other resources, it returns a direct pointer to the desired resource instead of a copy. This causes an aliasing issue where modifications to the resolved resource inadvertently affect the desired resource.
Impact: When the ACK runtime adds conditions to the resolved resource (particularly on certain errors), these conditions are also applied to the desired resource since both variables point to the same object. This causes the status patch operation to fail detecting any differences, preventing condition updates from being persisted.
With these changes, we will start returning the copy of desired object if the object returned
by the controllers is nil.
If not, we will continue use the returned object.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.