hashicorp / terraform-provider-aws

The AWS Provider enables Terraform to manage AWS resources.
https://registry.terraform.io/providers/hashicorp/aws
Mozilla Public License 2.0
9.85k stars 9.2k forks source link

[Bug]: RDS blue green deployment unexpected behaviour of switchover. #40238

Open sp055201 opened 4 days ago

sp055201 commented 4 days ago

Terraform Core Version

1.9.8

AWS Provider Version

5.75.1

Affected Resource(s)

aws_db_instance

Expected Behavior

Create Blue/Green deployment at T0, user should be able to apply the changes to the Green instance at T1 and perfrom the switch over to green instance at T2.

Actual Behavior

By enabling blue green deployment using below

blue_green_update { enabled = true } apply_immediately=true

AWS Terraform provider is automatically performing below steps without any further inout from the user.

  1. provisioning the green instance
  2. syncing it with the blue instance
  3. triggering the switchover
  4. deleting the old instance

There is no way user can control the switchover and deletion of old instance which is totally an unexpected behaviour.

The purpose of creating blue green deployment is to perform low downtime maintenance(including schema changes) by performing the changes on the green instance and perform a switchover when READY.

With the current behaviour , there is no use in creating a blue green deployment as user do not have control of step 3 and 4 mentioned above.

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

blue_green_update { enabled = true } apply_immediately=true

Steps to Reproduce

Please add the below block to aws postgresql RDS instance terraform configuration blue_green_update { enabled = true apply_immediately=true }

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None

github-actions[bot] commented 4 days ago

Community Note

Voting for Prioritization

Volunteering to Work on This Issue