Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(dbinstance): in isUpToDate consider 0 and nil to be equal for iops/storageThroughput #2037

Conversation

wotolom
Copy link
Contributor

@wotolom wotolom commented Apr 12, 2024

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) to gp2,

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:

  • Read and followed Crossplane's [contribution process].
  • Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

manually

…torageThroughput

Signed-off-by: Charel Baum (external expert on behalf of DB InfraGO AG) <charel.baum-extern@deutschebahn.com>
Copy link
Collaborator

@MisterMX MisterMX left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thank you very much @wotolom!

@MisterMX MisterMX merged commit 74140a2 into crossplane-contrib:master Apr 15, 2024
9 checks passed
Copy link

Successfully created backport PR #2040 for release-0.47.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants