fix: avoid returning resolved on error #219
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.