terraform-aws-rds-cluster
terraform-aws-rds-cluster copied to clipboard
Action of deleting serverlessv2_scaling_configuration has no effect
Describe the Bug
The serverlessv2_scaling_configuration can not be deleted.
Expected Behavior
No change should be detected.
From AWS's documentation, it seems there is no way to delete these settings. But the Terraform change makes it look like it's going to delete it. It will be great to not report this type of change (setting the value to null) until it can actually do it so the change doesn't have to reappear again and again.
Steps to Reproduce
- Create a regional RDS cluster with one writer with terraform.
- From the AWS console, add a reader with DB instance class
Serverless v2 - Delete the reader from the AWS console. Now if we click "Modify" on the cluster, we will see the leftover Serverless v2 capacity settings such as
Minimum ACUsandMaximum ACUs. - When we run
terraform plan, it always detects changes like:
~ serverlessv2_scaling_configuration {
- max_capacity = 128 -> null
- min_capacity = 2 -> null
}
But it won't actually change these settings or delete the whole Serverless v2 capacity settings section from the cluster when we terraform apply.
5. When we rerun terraform plan, the above change will show up again.
Screenshots
No response
Environment
- Module version: 0.44.0
- Terraform version: 1.3.2
Additional Context
No response