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

providers/aws: Fix issue with VPC Classic Link and regions that don't support it #4879

Merged
merged 1 commit into from
Jan 28, 2016

Conversation

catsby
Copy link
Contributor

@catsby catsby commented Jan 28, 2016

Fixes regression introduced into #3994 (reported in #4874) by only reading/storing the classic value for regions that support it

… support it

- use eu-central-1 to a config to check for #4874
- update documentation
@phinze
Copy link
Contributor

phinze commented Jan 28, 2016

LGTM

catsby added a commit that referenced this pull request Jan 28, 2016
providers/aws: Fix issue with VPC Classic Link and regions that don't support it
@catsby catsby merged commit dd0475c into master Jan 28, 2016
@catsby catsby deleted the b-aws-vpc-classiclink-fix branch January 28, 2016 16:59
@ghost
Copy link

ghost commented Apr 28, 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 28, 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.

2 participants