-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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: Change RDS variable iops
default value from 0
to null
#456
fix: Change RDS variable iops
default value from 0
to null
#456
Conversation
iops
default value from 0
to null
iops
default value from 0
to null
iops
default value from 0
to null
iops
default value from 0
to null
iops
default value from 0
to null
iops
default value from 0
to null
iops
default value from 0
to null
iops
default value from 0
to null
@@ -180,7 +180,7 @@ variable "multi_az" { | |||
variable "iops" { | |||
description = "The amount of provisioned IOPS. Setting this implies a storage_type of 'io1'" | |||
type = number | |||
default = 0 | |||
default = null |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I honestly have no idea if there is a good reason or not for the default value currently been 0
.
The only thing I know: this is currently causing an incompatibility with the default behavior of the AWS Provider in his version 4.46.0
.
Someone, not using terraform-aws-rds
module, can directly transition from gp2
to gp3
(see: hashicorp/terraform-provider-aws#28271 (comment))
But using terraform-aws-rds
, you are forced to override the default value of iops
from 0
, to null
:
hashicorp/terraform-provider-aws#28271 (comment)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
its optional so null
should be the appropriate default value
you'll need to run |
Thanks for the hint @bryantbiggs! I was looking for it before attempting my manual modification. Hope it's good now 🤞 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you!
Thanks for your help putting it together 🤝 |
### [5.2.1](v5.2.0...v5.2.1) (2022-12-14) ### Bug Fixes * Change RDS variable `iops` default value from `0` to `null` ([#456](#456)) ([9c8d21f](9c8d21f))
This PR is included in version 5.2.1 🎉 |
Hi! I don't know if this is the best place to comment this (please point me to the right one if it's the case), but this PR kinda misses one case: the change was only applied to |
Thanks for pointing this out @lucasvuotto, will replicate my recent changes in the main module, starting with: |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Description
The RDS variable
iops
is currently having a default of0
.In this PR, I propose that the default value become
null
and so to avoid side effects on the AWS Provider side.Motivation and Context
The current default value is causing side effects for people currently trying to adopt
gp3
(see: hashicorp/terraform-provider-aws#28271)Breaking Changes
No idea, could be, but I have the feeling not.
How Has This Been Tested?
Not tested yet, just proposing the idea