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

provider/aws: Fix Lambda VPC integration (missing vpc_id field) #6157

Merged
merged 2 commits into from
Apr 13, 2016

Conversation

radeksimko
Copy link
Member

I'm not sure whether this field wasn't there before and was added in later versions of SDK or whether it was just overlooked - I assume the latter since it was already part of flattenLambdaVpcConfigResponse.

The vpc_config field was never saved as d.Set was failing due to missing field in the schema and that was also triggering unnecessary updates.

@catsby
Copy link
Contributor

catsby commented Apr 13, 2016

LGTM

@ghost
Copy link

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