Open prudhvi opened 2 years ago
One of the debug log contains this warning message, not sure if it's related
-----------------------------------------------------: timestamp=2022-01-27T06:04:07.827Z
2022-01-27T06:04:07.828Z [INFO] plugin.terraform-provider-aws_v3.73.0_x5: 2022/01/27 06:04:07 [DEBUG] [aws-sdk-go] {"Tags":[{"Key":"Environment","Value":"staging"},{"Key":"Service","Value":"prudhvi-test"}]}: timestamp=2022-01-27T06:04:07.827Z
2022/01/27 06:04:07 [WARN] Provider "registry.terraform.io/hashicorp/aws" produced an unexpected new value for aws_dynamodb_table.west, but we are tolerating it because it is using the legacy plugin SDK.
The following problems may be the cause of any confusing errors from downstream operations:
- .write_capacity: was cty.NumberIntVal(500), but now cty.NumberIntVal(0)
- .read_capacity: was cty.NumberIntVal(500), but now cty.NumberIntVal(0)
- .billing_mode: was cty.StringVal("PROVISIONED"), but now cty.StringVal("PAY_PER_REQUEST")
We still encountered this with provider version 4.67
Community Note
Terraform CLI and Terraform AWS Provider Version
TERRAFORM_VERSION=0.14.11 TERRAFORM_AWS_PROVIDER_VERSION=3.73.0
Affected Resource(s)
Terraform Configuration Files
Debug Output
Expected Behavior
Should change the table billing mode and also attach the autoscaling settings that are supplied in terraform
Actual Behavior
Failed to change the table from PAY_PER_REQUEST to PROVISIONED billing and add autoscaling at the same time. Updated the billing mode to PROVISIONED but failed to attach the autoscaling settings. Even after adding
depends_on
for autoscaling resources so that table update finishes before applying the autoscaling settings it's not working.My guess is that
depends_on
doesn't actually wait for the table to becomeACTIVE
before applying the autoscaling targetsSteps to Reproduce
terraform apply