Same behavior as deployment_type = SINGLE_AZ_1 where throughput_capacity should not be trying to perpetually update.
Actual Behavior
Plan shows ~ throughput_capacity = 0 -> 1536
aws_fsx_ontap_file_system.v2: Refreshing state... [id=fs-0f228a513fa1da191]
aws_fsx_ontap_file_system.v1: Refreshing state... [id=fs-0d161cf0b3d8a72d3]
Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the
following symbols:
~ update in-place
Terraform will perform the following actions:
# aws_fsx_ontap_file_system.v2 will be updated in-place
~ resource "aws_fsx_ontap_file_system" "v2" {
id = "fs-0f228a513fa1da191"
tags = {}
~ throughput_capacity = 0 -> 1536
# (21 unchanged attributes hidden)
# (1 unchanged block hidden)
}
Plan: 0 to add, 1 to change, 0 to destroy.
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
Volunteering to Work on This Issue
If you are interested in working on this issue, please leave a comment.
If this would be your first contribution, please review the contribution guide.
Terraform Core Version
1.9.3
AWS Provider Version
5.61.0
Affected Resource(s)
Expected Behavior
Same behavior as
deployment_type = SINGLE_AZ_1
wherethroughput_capacity
should not be trying to perpetually update.Actual Behavior
Plan shows
~ throughput_capacity = 0 -> 1536
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
terraform apply --auto-approve
terraform plan
aws_fsx_ontap_file_system
of typeSINGLE_AZ_2
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None