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

aws: Add new region (Mumbai) #7383

Merged
merged 2 commits into from
Jun 28, 2016

Conversation

radeksimko
Copy link
Member

@radeksimko radeksimko commented Jun 28, 2016

https://aws.amazon.com/about-aws/whats-new/2016/06/announcing-the-aws-asia-pacific-mumbai-region/

New ID verifiable via

aws ec2 describe-regions | jq .Regions[].RegionName | sort

@stack72
Copy link
Contributor

stack72 commented Jun 28, 2016

Nice work! LGTM! Merge when ready

@radeksimko radeksimko merged commit 68bb58d into hashicorp:master Jun 28, 2016
@radeksimko radeksimko deleted the f-aws-india-region branch June 28, 2016 11:18
@stephenchu
Copy link
Contributor

Mind me asking, why is Terraform keeping a list of hardcoded regions for its purpose?

@radeksimko
Copy link
Member Author

why is Terraform keeping a list of hardcoded regions for its purpose?

I think this is purely for static/offline validation of the aws provider configuration - so that the user gets a human-friendly error for cases like this:

provider "aws" {
  region = "not-exists"
}

We cannot verify this online, even though it's available from the API, because we'd need to choose a valid region (and hard-coding a single region is not a good idea since that region becomes a single point of failure) + have valid credentials so this is kind of a 🐔 & 🍳 problem when validating provider which is responsible for setting up the connection.

Also the way most SDKs work is that they simply take the given region as a string and make a hostname of it, so the error message user would see if Terraform wouldn't perform this offline validation is something like this:

Could not connect to the endpoint URL: "https://sts.not-exists.amazonaws.com/"

What I think would make sense to do though is to keep such list of valid regions in the SDK and let the SDK perform the validation, but SDK doesn't currently offer such functionality neither a list of regions.

@boxrick
Copy link

boxrick commented Jun 29, 2016

Will this make it into the RC3 at some point shortly?

@stack72
Copy link
Contributor

stack72 commented Jun 29, 2016

@boxrick not sure what the release plans are - that's a question for @phinze :)

@boxrick
Copy link

boxrick commented Jul 25, 2016

@phinze Will this make it into TF 0.7? Fairly simple change but it is stopping some work and I would appreciate if it could be merged in :)

@stack72
Copy link
Contributor

stack72 commented Jul 25, 2016

Hi @boxrick

this has already been merged - so it will definitely be in 0.7

Paul

@stack72
Copy link
Contributor

stack72 commented Jul 25, 2016

FWIW, it's already part of the RC3

@radeksimko
Copy link
Member Author

@stephenchu FYI - I just opened #11358 to add skip_region_validation. Feedback welcomed there.

@ghost
Copy link

ghost commented Apr 17, 2020

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.

@ghost ghost locked and limited conversation to collaborators Apr 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants