Closed fullheart closed 3 months ago
Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.
If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Community Note
Terraform CLI and Terraform AWS Provider Version
terraform -v
Affected Resource(s)
Terraform Configuration Files
Initial State
variable "elasticache_subnet_name" { default = "redis-subgroup-sandbox" }
After removing
aws_elasticache_cluster
ressourcevariable "elasticache_subnet_name" { default = "redis-subgroup-sandbox" }
Output from
terraform apply
Expected Behavior
When remove a
aws_elasticache_cluster
ressource, terraform should not throwRequested new replica count already matches current number of replicas.
error, when executeterraform apply
. Because its obvious (from my perspective) that , that the attributenumber_cache_clusters
decrease by 1, when remove 1aws_elasticache_cluster
ressource.Actual Behavior
Get Error (see log above).
Steps to Reproduce
variable.tf
andelasticache.tf
file (seeInitial State
above)terraform apply
elasticache.tf
like mentioned above inAfter removing aws_elasticache_cluster ressource
sectionterraform apply