-
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
(custom-resources): broken usage of list tokens in parameters #14088
Comments
Not sure what to make of the following:
Is the first one broken, the 2nd one a workaround?
Is confusing me a little because it would end up as |
❤️ on the repro though. Feature haz test but I can confirm this example fails. Hey-ho, a-digging we will go |
😳 Must be because of separate prepare/synth cycles. 🤬 |
Oooh sorry, yeah the second one was an attempt at a workaround but both failed. |
For reasons explained in the previous PR, list tokens need to be run through a custom resource. This custom resource gets added during token resolution, but because that is run multiple times the side effect of adding the custom resource gets executed multiple times. Add a cache to make sure the second execution returns the first answer as the first one. Not a fantastic solution, but given the constraints of Lazies, I'm not sure we can do any better. Fixes #14088.
…14138) For reasons explained in the previous PR, list tokens need to be run through a custom resource. This custom resource gets added during token resolution, but because that is run multiple times the side effect of adding the custom resource gets executed multiple times. Add a cache to make sure the second execution returns the first answer as the first one. Not a fantastic solution, but given the constraints of Lazies, I'm not sure we can do any better. Fixes #14088. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
…ws#14138) For reasons explained in the previous PR, list tokens need to be run through a custom resource. This custom resource gets added during token resolution, but because that is run multiple times the side effect of adding the custom resource gets executed multiple times. Add a cache to make sure the second execution returns the first answer as the first one. Not a fantastic solution, but given the constraints of Lazies, I'm not sure we can do any better. Fixes aws#14088. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Referencing a token that is a list of strings within a custom resource parameters object results in a reference to an undefined parameter.
Reproduction Steps
Reproduction App
What did you expect to happen?
Deploys the app to cloudformation with the CR having access to the vpce network interface IDs as json.
What actually happened?
cdk deploy
results inEnvironment
Other
Related to some recent changes:
#13465
#13544
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: