Open ghost opened 5 years ago
@aeschright / @bflad - Is this issue resolved in the provider?
@jsanant For what it's worth, I just ran into this with the latest provider and the proposed workaround is still working.
Any update or even any response from team? This is happening again Terraform 0.12.26 with aws provider 3.7.
Also met this issue, with Terraform 0.14.3 and aws provider 3.37.0
Just faced this with Terraform 1.0.4 and AWS provider 3.52.0.
Running into same scenario w/ Terraform 1.1.6, AWS provider 4.2.0
This issue still exists for us..
+1 Just ran into this on Terraform 1.1.7 and AWS provider 4.20.1 It has been almost 4 years since this issue was first reported.
+1 I too ran into this issue on Terraform v1.3.7.
This issue still exists on Terraform 1.3.7 and AWS provider v4.50.0
unbelievable, this is from 2019 and still not fixed
Still facing this issue while running terraform version 1.5.2
This is still an issue 6 years later with Terraform 1.6.6.
This issue was originally opened by @ngkuznetsov as hashicorp/terraform#19336. It was migrated here as a result of the provider split. The original body of the issue is below.
Terraform Version
Terraform Configuration Files
Expected Behavior
Terrafom changes snapshot configuration of Elasticache Redis cluster, which is restored from an automatic backup.
Actual Behavior
Terraform apply against restored from backup Elasticache Redis cluster fails with the error:
Steps to Reproduce
Snapshot configuration:
Always Redis cluster is restored from a backup to a NEW Cluster. The new cluster is restored with default snapshot configuratations:
Restored redis configuration:
terraform apply
for changing Elasticache Redis cluster configuration and get the error:Workaround
snapshot_retention_limit
>0 and <35 setsnapshot_window
to any value like20:00-23:00