Skip to content
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

[Bug]: "blue_green_update.enabled" cannot be set when "engine" is "postgres". #34317

Closed
dpedu opened this issue Nov 8, 2023 · 3 comments
Closed
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/rds Issues and PRs that pertain to the rds service.

Comments

@dpedu
Copy link

dpedu commented Nov 8, 2023

Terraform Core Version

1.5

AWS Provider Version

5.24.0

Affected Resource(s)

  • aws_db_instance

Expected Behavior

Terraform upgrades the db instance using a blue/green deployment

Actual Behavior

Terraform decides it cannot upgrade the db instance:

│ Error: 1 error occurred:
│ 	* "blue_green_update.enabled" cannot be set when "engine" is "postgres".

Relevant Error/Panic Output Snippet

│ Error: 1 error occurred:
│ 	* "blue_green_update.enabled" cannot be set when "engine" is "postgres".

Terraform Configuration Files

N/a

Steps to Reproduce

N/a

Debug Output

No response

Panic Output

No response

Important Factoids

Support for blue/green upgrades for postgres under RDS was introduced recently:

https://aws.amazon.com/blogs/database/new-fully-managed-blue-green-deployment-in-amazon-aurora-postgresql-and-amazon-rds-for-postgresql/

Why the provider previously needed this check instead of bouncing off the aws api is beyond me.

References

No response

Would you like to implement a fix?

None

@dpedu dpedu added the bug Addresses a defect in current functionality. label Nov 8, 2023
Copy link

github-actions bot commented Nov 8, 2023

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please see our prioritization guide for information on how we prioritize.
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@github-actions github-actions bot added the service/rds Issues and PRs that pertain to the rds service. label Nov 8, 2023
@terraform-aws-provider terraform-aws-provider bot added the needs-triage Waiting for first response or review from a maintainer. label Nov 8, 2023
@ewbankkit ewbankkit added enhancement Requests to existing resources that expand the functionality or scope. and removed bug Addresses a defect in current functionality. needs-triage Waiting for first response or review from a maintainer. labels Nov 8, 2023
@ewbankkit
Copy link
Contributor

@dpedu Thanks for raising this issue 👏.
This has been addressed via #34216 which will be released with Terraform AWS Provider v5.25.0, likely tomorrow.

Copy link

github-actions bot commented Dec 9, 2023

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 9, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/rds Issues and PRs that pertain to the rds service.
Projects
None yet
Development

No branches or pull requests

2 participants