Skip to content

AWS partition is hardcoded to aws in multiple resources which prevent user to use this module in china or gov aws accounts. #671

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

Closed
1 task done
vladislav-orlovskiy opened this issue Apr 7, 2025 · 2 comments

Comments

@vladislav-orlovskiy
Copy link
Contributor

vladislav-orlovskiy commented Apr 7, 2025

Description

module contains multiple outputs and policies that has hardcoded aws partition in them

#670 list's all affected resources

  • ✋ I have searched the open/closed issues and my issue is not listed.

⚠️ Note

Before you submit an issue, please perform the following first:

  1. Remove the local .terraform directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!): rm -rf .terraform/
  2. Re-initialize the project root to pull down modules: terraform init
  3. Re-attempt your terraform plan or apply and check if the issue still persists

Versions

  • Module version [Required]:

  • Terraform version:

Terraform v1.11.1

  • Provider version(s):
  • provider registry.terraform.io/hashicorp/aws v5.94.0

Steps to reproduce the behavior:

  1. deploy module example in china region

Expected behavior

partition in policies and outputs should be same as aws account partition (for ex: for china its aws-cn )

Actual behavior

partition is hardcoded to aws

@antonbabenko
Copy link
Member

Fixed in #670. Released in v7.20.2.

Copy link

github-actions bot commented May 9, 2025

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 May 9, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants