iops not undefinable on an aws_ebs_volume violates standards

[gtmtech]

Terraform 0.11.1

mitchellh 's comment on hashicorp/terraform#5471 says that resources must interpret a zero value to be undefined.

iops on an aws_ebs_volume when set to "" says:

Error: module.server.aws_ebs_volume.server_disk2: iops: cannot parse '' as int: strconv.ParseInt: parsing "": invalid syntax

For this reason it is currently impossible to write a module for an aws_ebs_volume which can parameterise whether iops are included or not.

[matthiasr]

is the empty string the zero value for integers?

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

[matthiasr]

I believe this can be closed. At least as of Terraform 0.14, and with provider 3.x, defaulting the variable to null does the right thing.