fix: change syncTableTags parameter order to avoid panic #136
+2
−2
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 #2459#issuecomment-2886623397
Description of changes:
In syncTableTags, there was an issue with the order/naming of desired vs
latest resource.
Although the function is called using
syncTableTags(desired, latest)
the function definition had
syncTableTags(latest, desired)
. Thisbecomes an issue when we try to retrieve the ARN from latest, during
adoption.
Although in the funciton we named the parameter
latest
, this parameterwas treated as the desired resource when computing the tags delta.
During adoption, the Status/ARN of the desired resource is meant to be
nil, unitl it is later populated. Hence our need to use the ARN from
latest.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.