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 Aurora Blue/Green Update #28956
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Additionally, support for manually managing blue-green deployment resources would be nice, for longer-running validation or more complex scenarios. |
It would be great to get this prioritised. Major version upgrades with Terraform are currently incredibly painful without this feature. |
Yup, big thumbs up to this. |
I'm volunteering to work on this issue, this is going to be PR number 7 of my hundred days of Terraform contributions challenge. |
There was no testing available for the map method, creating a new resource so we can actually have tests for this. |
This is about 75 percent done, but given RDS Aurora takes 40 minutes or so for a full deployment on each run plus 20 minutes (haven't timed the deletion period yet exactly) or so to delete, it has taken some time to create, read, update, and delete the resource code and test. If you could evaluate what I've got so far once the linter checks are fixed in the second PR noted above that would be great, if you plan to take it over and do your own version/rewrite it would be greatly appreciated if you could let me know. |
I am in the same boat. Big thumbs up to this functionality. This feature would be a significant improvement and prioritizing it would be beneficial, as DB/maintenance upgrades are currently quite challenging without |
Thank you all for the discussion here. Unfortunately, Blue/Green Deployments would not work the same with with Aurora clusters as they do with A stand-alone resource for RDS Blue/Green Deployments does not fit with the Terraform model of declarative infrastructure: Using the resource would require multiple iterations of editing the Terraform configuration, applying the configuration, or importing resources. A separate tool that can manage the orchestration steps would be a better fit. For more details, see #34551 |
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. |
Description
blue_green_update
is valid only foraws_db_instance
and does not work withaws_rds_cluster_instance
. As per the documentationaws_rds_cluster_instance
is the recommended way to manage aurora instance. If that is the case,blue_green_update
should work with Auroa. (aws_rds_cluster_instance)Affected Resource(s) and/or Data Source(s)
aws_rds_cluster, aws_rds_cluster_instance
Potential Terraform Configuration
No response
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: