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

gp3 storage type also supports providing iops manually when storage is atleast 400gb. #168

Closed
ankitjethi opened this issue Jan 25, 2024 · 1 comment · Fixed by #176
Closed
Labels
bug 🐛 An issue with the system

Comments

@ankitjethi
Copy link

Describe the Bug

We created a RDS database with gp3 storage type and then after that on the next terraform apply, it is is changing the iops from 3000 to 0.

Expected Behavior

it should not change to 0. it should stay at 3000 for storage size under 400gb.
And let us customize IOPS for greater that 400gb.

Steps to Reproduce

create a gp3 RDS with less than 400gb storage and then re-run terraform apply.

Screenshots

Screenshot 2024-01-25 at 7 32 24 PM

Environment

No response

Additional Context

No response

@ankitjethi ankitjethi added the bug 🐛 An issue with the system label Jan 25, 2024
@kbolino
Copy link
Contributor

kbolino commented Apr 15, 2024

Specifically, the issue here seems to be that the iops variable in this module has a default of 0 when it should have a default of null. Explicitly setting iops = null when calling the module fixes the issue.

kbolino added a commit to kbolino/terraform-aws-rds that referenced this issue Apr 15, 2024
gberenice pushed a commit that referenced this issue Apr 15, 2024
* fix: Default iops to null (#168)

* chore: Update instance type in test fixture
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 An issue with the system
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants