-
Notifications
You must be signed in to change notification settings - Fork 4k
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-ec2: Cannot create VPC Endpoint using existing VPC & Subnets if cdk.context.json is missing VPC information #17600
Labels
@aws-cdk/aws-ec2
Related to Amazon Elastic Compute Cloud
bug
This issue is a bug.
effort/small
Small work item – less than a day of effort
p2
Comments
sdobberstein
added
bug
This issue is a bug.
needs-triage
This issue or PR still needs to be triaged.
labels
Nov 19, 2021
github-actions
bot
added
the
@aws-cdk/aws-ec2
Related to Amazon Elastic Compute Cloud
label
Nov 19, 2021
njlynch
added
effort/small
Small work item – less than a day of effort
and removed
needs-triage
This issue or PR still needs to be triaged.
labels
Dec 8, 2021
rix0rrr
added a commit
that referenced
this issue
Jan 20, 2022
The validation was too eager, causing a validation error before the actual lookup happened. Add a property to `SelectedSubnets` to make it clear in consuming code that validation shouldn't happen yet. Fixes #17600.
mergify bot
pushed a commit
that referenced
this issue
Jan 20, 2022
…8554) The validation was too eager, causing a validation error before the actual lookup happened. Add a property to `SelectedSubnets` to make it clear in consuming code that validation shouldn't happen yet. Fixes #17600. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
TikiTDO
pushed a commit
to TikiTDO/aws-cdk
that referenced
this issue
Feb 21, 2022
…s#18554) The validation was too eager, causing a validation error before the actual lookup happened. Add a property to `SelectedSubnets` to make it clear in consuming code that validation shouldn't happen yet. Fixes aws#17600. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Hello, this issue is still happening. Any update on the fix? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
@aws-cdk/aws-ec2
Related to Amazon Elastic Compute Cloud
bug
This issue is a bug.
effort/small
Small work item – less than a day of effort
p2
What is the problem?
If you have a stack where you need to look up an existing VPC (using
VPC.fromLookup
) and add a VPC Interface Endpoint to it using a subnet selection, it will fail if thecdk.context.json
file does not exist or does not contain information about that VPC already.Reproduction Steps
Assumptions:
Steps to Reproduce:
Populate Account, Subnet Ids, and VPC Id
Ensure
cdk.context.json
either doesn't exist, or at least does not contain information matching your VPCRun
cdk ls
Verify error occurs
Workaround:
cdk ls
which should create/update thecdk.context.json
cdk ls
and it should workCode:
What did you expect to happen?
I should be able to run CDK commands without an error occurring and without having to comment out portions of my stack in order to generate/update the
cdk.context.json
file.What actually happened?
All CDK commands fail with an error and the
cdk.context.json
file is not generated/updated.CDK CLI Version
1.132.0
Framework Version
No response
Node.js Version
v14.17.5
OS
macOS 11.5.1
Language
Typescript
Language Version
TypeScript (3.9.10)
Other information
The error that you will see after running any CDK command is:
Reference implementation: https://github.com/sdobberstein/cdk-vpc-issue
The text was updated successfully, but these errors were encountered: