-
-
Notifications
You must be signed in to change notification settings - Fork 184
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
Aurora Serverless "BackupWindow" parameter not working #81
Comments
@sebastianmacarescu thanks for reporting this. |
Tried to set it to null but I get validation error, preferred_maintenance_window must be of format ... |
+1 |
From this commit e82b41f @joshmello @sebastianmacarescu does it work if you tried setting the following to null ? maintenance_window = null
backup_window = null
retention_period = null |
@nitrocode when I tested last year no, it did not work setting to null. |
It seems like an aws api issue. A serverless aurora does have these parameters and these can be modified in the browser but not from the aws api. The workaround from the issue you linked above is to comment out the You can see from the below code we're passing in the input vars unaltered to the corresponding resource. terraform-aws-rds-cluster/main.tf Line 61 in 28e76de
terraform-aws-rds-cluster/main.tf Line 71 in 28e76de
terraform-aws-rds-cluster/main.tf Line 143 in 28e76de
terraform-aws-rds-cluster/main.tf Line 153 in 28e76de
Looks like a user has documented that serverless engine mode has a few limitations which could be worked around by the aws provider. aws-cloudformation/cloudformation-coverage-roadmap#396 (comment) @joshmello @sebastianmacarescu you may have better luck creating another ticket with the aws provider. When you do, please include a minimal example using the raw resource |
Describe the Bug
It seems like AWS does not support (or maybe is bugged) "preferred_maintenance_window " and "preferred_backup_window"
Existing AWS issue: aws-cloudformation/cloudformation-coverage-roadmap#396
This was also reported internally in AWS team
Expected Behavior
Everything should work as expected
Steps to Reproduce
Steps to reproduce the behavior:
Screenshots
Create a serverless database from a snapshot. Right after it's finished terraform will throw:
Error: error modifying RDS Cluster (tc-staging-shared-main-rds): InvalidParameterCombination: You currently can't modify BackupWindow with Aurora Serverless. status code: 400, request id: aa5042ba-f0be-49ea-a695-e68da91a01f8
If you run terraform again it will say the cluster is tainted and must be replaced.
Moreover a lot of values are just wrong. The created resource has totally different values than specified in terraform code:
Environment (please complete the following information):
Additional Context
I think you could have a dedicated resource for serverless clusters with the above fields omitted
The text was updated successfully, but these errors were encountered: