-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
[cloudformation] NestedStack doesn't have defaultChild #11221
Comments
You are very correct. It needs to be assigned as it has a non-standard name. |
@rix0rrr is there a workaround in the mean time? I'm confused from your answer because if I call the |
I have also tried this on version 1.71.0 with the same result. |
I found the workaround for |
@rix0rrr created a PR for this (my first) |
fixes #11221 ---- ### All Submissions: * [x] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/master/CONTRIBUTING.md) ### Adding new Unconventional Dependencies: * [ ] This PR adds new unconventional dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/master/CONTRIBUTING.md/#adding-new-unconventional-dependencies) ### New Features * [ ] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/master/INTEGRATION_TESTS.md)? * [ ] Did you use `yarn integ` to deploy the infrastructure and generate the snapshot (i.e. `yarn integ` without `--dry-run`)? *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
I get an
undefined
object when I access the attributedefaultChild
from aNestedStack
's node.Reproduction Steps
I tried this code on https://play-with-cdk.com/
What did you expect to happen?
The stack to be synthesized without errors and with the
TemplateURL
parameter of the stack overriden.What actually happened?
The synth crashes with this error:
Environment
I have also tried it with Python and the same error happens.
Other
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: