Terraform-provider-aws: aws_fsx_windows_file_system minimum storage capacity does not match console

Created on 11 Dec 2019  ·  5Comments  ·  Source: hashicorp/terraform-provider-aws

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

 [master ≡ +0 ~1 -0 !]> terraform -v
Terraform v0.12.15
+ provider.aws v2.41.0

Affected Resource(s)

  • aws_fsx_windows_file_system

Terraform Configuration Files

resource "aws_fsx_windows_file_system" "filecluster" {
    storage_capacity    = 32
    throughput_capacity = 128
  active_directory_id = data.terraform_remote_state.directory.outputs.directory_id

  subnet_ids          = [
        data.aws_subnet.service[0].id
    ]

  security_group_ids  = [
    data.aws_security_group.vpc.id
  ]
}

Expected Behavior

Support storage capacity as per GUI console:

Minimum 32 GiB; Maximum 65536 GiB

Actual Behavior

Error: expected storage_capacity to be in the range (300 - 65536), got 32

References

For Windows file systems, valid values are 32 GiB - 65,536 GiB.

enhancement servicfsx

Most helpful comment

All 5 comments

@pmcevoy, @bflad, I wrote a patch for this (#11272), hope it works. It's my first contribution here. I wasn't familiar with the test suite but it seemed to work in the second iteration (I closed the first PR).

Validation for the lower storage_capacity minimum value has been merged and will release with version 2.43.0 of the Terraform AWS Provider, tomorrow. Thanks to @mrgiles for the implementation. 👍

This has been released in version 2.43.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks!

I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

Was this page helpful?
0 / 5 - 0 ratings