Revert upjet changes around calculating instance diff in 0.47 #1104
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 your changes
This rolls back the upjet version in the provider-aws release-0.47 branch to resolve errors thrown when calculating instance diffs.
Somewhere in crossplane/upjet#317, crossplane/upjet#319 and/or crossplane/upjet#324 there was a change introduced in upjet related to calculating terraform instance diffs, that was included in provider-aws 0.47.0, and which seems to be the cause of errors relating to nil/zero values on several different resources.
Unfortunately, a linear revert to an earlier commit in the
main
branch on upjet won't work, because there was a forwards-incompatible schema change that would be a breaking change to revert (and is unrelated to this issue).I opened crossplane/upjet#333, to roll back upjet to that commit, and then built this off of that revision.
Fixes #1071
I have:
make reviewable test
to ensure this PR is ready for review.How has this code been tested
Uptest