-
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
[ec2] Volume construct throws with fresh CDK app #9081
Comments
@ddneilson I was not able to repro this issue with 1.51 in us-east-1. The stack created with no errors. |
@ericzbeard Don't know what to tell you. I can reproduce it every time I try...
|
When the |
That's certainly easy. Will get that up right now as a change to the attached PR. |
This fixes an erroneous validation failure of the `availabilityZone` property of the `Volume` construct that occurs during the first run of a fresh application. Fixes: #9081 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
This fixes an erroneous validation failure of the `availabilityZone` property of the `Volume` construct that occurs during the first run of a fresh application. Fixes: aws#9081 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
If you have an app with an
aws-ec2.Volume
within it, then that app will throw a failed validation exception during the first fresh run of the app. This is because the VPC is not set up with true availability zones during this first run; instead it is set up with a dummy VPC -aws-cdk/packages/@aws-cdk/aws-ec2/lib/vpc.ts
Line 1941 in b0f8729
Reproduction Steps
Error Log
Environment
Other
The
Volume
code was introduced in #8219This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: