fix: ensure resource status is patched before checking for updates on #213
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.
Issue #2693
Description of changes:
Currently, when a resource has the
adopt-or-createannotation,and the controller successfully adopts the resource, we immediately
check if there are any deltas and make an update call if needed.
This has been problematic for some controllers, since most return
the
desiredstatus (which will be empty during adopt-or-create).This change ensures we update the resource status with the latest
information from AWS, requeue and handle any updates if needed,
ensuring no information is lost.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.