-
Notifications
You must be signed in to change notification settings - Fork 9.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't enable automatic snapshotting on aws_elasticache_replication_group #10581
Comments
Hi @Alars-ALIT Sorry for the issue here. From the error message I am assuming things go down as follows:
This correct? I am trying to recreate this right now and am struggling to do so. Any help would be great Paul |
Replicated it :)
|
Fixes: #10581 When a cluster was originally created, you could not enable snapshotting on it. An error message like this was found: ``` * aws_elasticache_replication_group.bar: Error updating Elasticache replication group: InvalidParameterCombination: Must specify both SnapshotRetentionLimit and SnapshottingClusterId to turn on snapshots status code: 400, request id: 98d2ea4e-3fb1-11e7-b077-5967719aeab4 ``` There is no guidance from AWS on which is the preferred Cluster in the RG to use for snapshotting. Therefore, I decided to set it to be the first cluster. We can now enable snapshotting
Fixes: #10581 When a cluster was originally created, you could not enable snapshotting on it. An error message like this was found: ``` * aws_elasticache_replication_group.bar: Error updating Elasticache replication group: InvalidParameterCombination: Must specify both SnapshotRetentionLimit and SnapshottingClusterId to turn on snapshots status code: 400, request id: 98d2ea4e-3fb1-11e7-b077-5967719aeab4 ``` There is no guidance from AWS on which is the preferred Cluster in the RG to use for snapshotting. Therefore, I decided to set it to be the first cluster. We can now enable snapshotting
Fixes: #10581 When a cluster was originally created, you could not enable snapshotting on it. An error message like this was found: ``` * aws_elasticache_replication_group.bar: Error updating Elasticache replication group: InvalidParameterCombination: Must specify both SnapshotRetentionLimit and SnapshottingClusterId to turn on snapshots status code: 400, request id: 98d2ea4e-3fb1-11e7-b077-5967719aeab4 ``` There is no guidance from AWS on which is the preferred Cluster in the RG to use for snapshotting. Therefore, I decided to set it to be the first cluster. We can now enable snapshotting ``` % make testacc TEST=./builtin/providers/aws/ TESTARGS='-run=TestAccAWSElasticacheReplicationGroup_enableSnapshotting' ==> Checking that code complies with gofmt requirements... go generate $(go list ./... | grep -v /terraform/vendor/) 2017/05/23 15:02:21 Generated command/internal_plugin_list.go TF_ACC=1 go test ./builtin/providers/aws/ -v -run=TestAccAWSElasticacheReplicationGroup_enableSnapshotting -timeout 120m === RUN TestAccAWSElasticacheReplicationGroup_enableSnapshotting --- PASS: TestAccAWSElasticacheReplicationGroup_enableSnapshotting (1261.47s) PASS ok github.com/hashicorp/terraform/builtin/providers/aws 1261.496s ```
…RG (#14757) Fixes: #10581 When a cluster was originally created, you could not enable snapshotting on it. An error message like this was found: ``` * aws_elasticache_replication_group.bar: Error updating Elasticache replication group: InvalidParameterCombination: Must specify both SnapshotRetentionLimit and SnapshottingClusterId to turn on snapshots status code: 400, request id: 98d2ea4e-3fb1-11e7-b077-5967719aeab4 ``` There is no guidance from AWS on which is the preferred Cluster in the RG to use for snapshotting. Therefore, I decided to set it to be the first cluster. We can now enable snapshotting ``` % make testacc TEST=./builtin/providers/aws/ TESTARGS='-run=TestAccAWSElasticacheReplicationGroup_enableSnapshotting' ==> Checking that code complies with gofmt requirements... go generate $(go list ./... | grep -v /terraform/vendor/) 2017/05/23 15:02:21 Generated command/internal_plugin_list.go TF_ACC=1 go test ./builtin/providers/aws/ -v -run=TestAccAWSElasticacheReplicationGroup_enableSnapshotting -timeout 120m === RUN TestAccAWSElasticacheReplicationGroup_enableSnapshotting --- PASS: TestAccAWSElasticacheReplicationGroup_enableSnapshotting (1261.47s) PASS ok github.com/hashicorp/terraform/builtin/providers/aws 1261.496s ```
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. |
Seems impossible to enable automatic snapshotting on a aws_elasticache_replication_group.
Terraform Version
0.7.13
Terraform Configuration Files
Debug Output
Error applying plan:
1 error(s) occurred:
status code: 400, request id: 25af6fe7-bc87-11e6-9afb-dd75999c5340
Expected Behavior
Snapshots should be enabled
Steps to Reproduce
terraform apply
The text was updated successfully, but these errors were encountered: