-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
aws-cdk-lib.aws_rds.DatabaseClusterProps: Deprecation Warnings #25898
Comments
We do offer a migration path, have you tried this out? https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_rds-readme.html#migrating-from-instanceprops |
This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled. |
Hi @peterwoodworth! Thanks I think it works now. I did specify the Some questions though:
|
|
Thank you @peterwoodworth! I will file separate issues to request for these features! |
Great @argarinpauljohn, I've triaged and responded to both of them, should be pretty easy for any contributors to implement 🙂. I think we can close this issue out now that we have two separate ones, ping me if you have any more concerns. |
|
Thanks @peterwoodworth! I will try to contribute! :) |
Describe the feature
So we fixed this by using writer and readers instead. But CDK will destroy the old database instances then recreate them. This isn't good for us as restoring the data in the new databases will require us more time and work. Would it be possible for the CDK team to handle the migration?
Use Case
It will be cumbersome backing up the data and restoring them especially in our production databases.
Proposed Solution
Handle the migration of data in the background?
Other Information
No response
Acknowledgements
CDK version used
2.82.0
Environment details (OS name and version, etc.)
macOS Ventura 13.3.1
The text was updated successfully, but these errors were encountered: