Skip to content

Conversation

@ValeriiStepanets
Copy link

@ValeriiStepanets ValeriiStepanets commented Oct 27, 2025

Small changes to blue_green_update block.

  • Added parameter_group_name to specify a custom DB param group in the time of green creation

Description

I'm working as a DevOps engineer and trying to perform a Major version upgrade using B/G deployment via Terraform.
Spotted an issue when I performed such an update - green environmet has the same param group as the blue one(with rds.logical_replication and other params that need for B/G update - but this will cause the error while replication), so I decided to add the possibility to specify custom db param group

Rollback Plan

If a change needs to be reverted, we will publish an updated version of the library.

Changes to Security Controls

Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.

Description

Relations

Closes #0000

References

Output from Acceptance Testing

% make testacc TESTS=TestAccXXX PKG=ec2

...

@ValeriiStepanets ValeriiStepanets requested a review from a team as a code owner October 27, 2025 13:06
@ValeriiStepanets ValeriiStepanets changed the title feat(bg-custom-param-group): add parameter_group_name for blue_green_… feat(bg-custom-param-group): add parameter_group_name for blue_green_update block Oct 27, 2025
@github-actions
Copy link
Contributor

Community Guidelines

This comment is added to every new Pull Request to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀

Voting for Prioritization

  • Please vote on this Pull Request by adding a 👍 reaction to the original post to help the community and maintainers prioritize it.
  • Please see our prioritization guide for additional information on how the maintainers handle prioritization.
  • Please do not leave +1 or other comments that do not add relevant new information or questions; they generate extra noise for others following the Pull Request and do not help prioritize the request.

Pull Request Authors

  • Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
  • Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.

@github-actions
Copy link
Contributor

github-actions bot commented Oct 27, 2025

✅ Thank you for correcting the previously detected issues! The maintainers appreciate your efforts to make the review process as smooth as possible.

@github-actions github-actions bot added needs-triage Waiting for first response or review from a maintainer. tests PRs: expanded test coverage. Issues: expanded coverage, enhancements to test infrastructure. service/rds Issues and PRs that pertain to the rds service. size/L Managed by automation to categorize the size of a PR. labels Oct 27, 2025
@justinretzolk justinretzolk added enhancement Requests to existing resources that expand the functionality or scope. and removed needs-triage Waiting for first response or review from a maintainer. labels Oct 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement Requests to existing resources that expand the functionality or scope. service/rds Issues and PRs that pertain to the rds service. size/L Managed by automation to categorize the size of a PR. tests PRs: expanded test coverage. Issues: expanded coverage, enhancements to test infrastructure.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants