fix(dbinstance): in isUpToDate consider 0 and nil to be equal for iops/storageThroughput #2037
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
AWS seems to be giving different responses for IOPS/StorageThroughput (either 0 or nil) depending on whether the instance was created as
gp2
or modified from another storageType (e.g.gp3
) togp2
,This changes their
isUptoDate()
checks to consider both 0 and nil to be equivalent.Also I used the opportunity and added missing parameters to the built diff for the logs.
I have:
make reviewable test
to ensure this PR is ready for review.How has this code been tested
manually