Skip to content

feat: Enhanced region support #509

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

feat: Enhanced region support #509

wants to merge 3 commits into from

Conversation

nightspotlight
Copy link

Description

Motivation and Context

This change will allow to simplify multi-region deployments of RDS resources. No longer need to maintain different provider aliases, one can simply pass region = "value" when calling the module. This will also allow for dynamic creation of multiple regional clusters with a for_each, like so:

locals {
  regions = toset(["us-east-1", "us-west-2", "eu-west-1"])
}

module "rds-aurora" {
  for_each = local.regions

  source = "terraform-aws-modules/rds-aurora/aws"

  region = each.value

  name = "rds-aurora-${each.value}"
}

Breaking Changes

Warning

AWS provider version 6.0.0 brings breaking changes, the list is extensive: https://github.com/hashicorp/terraform-provider-aws/releases/tag/v6.0.0

How Has This Been Tested?

  • I have updated at least one of the examples/* to demonstrate and validate my change(s)
  • I have tested and validated these changes using one or more of the provided examples/* projects
  • I have executed pre-commit run -a on my pull request

@nightspotlight
chore: pre-commit autoupdate
820f142
@nightspotlight
feat: add support for region (Enhanced Region Support)
1ff65a8 
- updated `aws` version constraint to `>= 6.0`
- added `region` input variable
- updated docs
@nightspotlight nightspotlight changed the title Enhanced region support feat: Enhanced region support Jun 25, 2025
@nightspotlight
Copy link
Author

This is draft until I can apply it at work in the scheduled window in two weeks, unless somebody else can pick up and test. Plans cleanly though in both my work project and examples/postgresql.

@nightspotlight nightspotlight marked this pull request as ready for review July 10, 2025 13:43
@nightspotlight
Copy link
Author

@antonbabenko , @bryantbiggs , ☝️😊

@bryantbiggs
Copy link
Member

I think theres a few more changes we'll want to make since its a breaking change. its on the list and we'll get to it soon

@bryantbiggs bryantbiggs mentioned this pull request Aug 8, 2025
Open
@github-actions GitHub Actions
Copy link

github-actions bot commented Sep 8, 2025

This PR has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this PR will be closed in 10 days

@github-actions github-actions bot added the stale label Sep 8, 2025
@nightspotlight
Copy link
Author

This PR has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this PR will be closed in 10 days

I believe it's still relevant and should be reviewed.

@github-actions github-actions bot removed the stale label Sep 9, 2025
@github-actions GitHub Actions
Copy link

This PR has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this PR will be closed in 10 days

@github-actions github-actions bot added the stale label Oct 10, 2025
@github-actions github-actions bot removed the stale label Oct 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

breaking change

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@nightspotlight @bryantbiggs