You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue was originally opened by @dattim as hashicorp/terraform#22378. It was migrated here as a result of the provider split. The original body of the issue is below.
Terraform Version
Terraform v0.12.2
Your version of Terraform is out of date! The latest version
is 0.12.6. You can update by downloading from www.terraform.io/downloads.html
Wed Aug 07 10:30:28
Expected Behavior
When I change global_secondary_index.read_capacity from 10 -> 60, terraform plan should show a change to the read_capacity for my global secondary index
Actual Behavior
When I change global_secondary_index.read_capacity from 10 -> 60, no changes are reported with terraform plan
Steps to Reproduce
Please list the full steps required to reproduce the issue, for example:
Create a dynamo db table with terraform
-- Set the read/write capacity for a global secondary index (not the table level read/write capacity) to 10 each
terraform apply to create the table in AWS
Change your terraform code to set the global secondary index read/write capacity to 60 each
terraform plan to see no changes to the global secondary index capacities
Additional Context
I'm using a dynamic block for the global_secondary_index, and a variable block to populate it
This also affects changes to the primary sort keys. When changing from a string type to a Number for example. The change is ignored and results in "No Changes"
Expected behavior in this case would be a destroy/create operation on the entire table. I felt like this was related so I'm posting this here
This issue was originally opened by @dattim as hashicorp/terraform#22378. It was migrated here as a result of the provider split. The original body of the issue is below.
Terraform Version
Expected Behavior
When I change
global_secondary_index.read_capacity
from10
->60
,terraform plan
should show a change to the read_capacity for my global secondary indexActual Behavior
When I change
global_secondary_index.read_capacity
from10
->60
, no changes are reported withterraform plan
Steps to Reproduce
Please list the full steps required to reproduce the issue, for example:
-- Set the read/write capacity for a global secondary index (not the table level read/write capacity) to 10 each
terraform apply
to create the table in AWSterraform plan
to see no changes to the global secondary index capacitiesAdditional Context
I'm using a dynamic block for the global_secondary_index, and a variable block to populate it
Providers:
References
https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_UpdateGlobalSecondaryIndexAction.html
^ This should be possible, according to the API docs.
The text was updated successfully, but these errors were encountered: