[core] transparent cross-stack references don't work in overrides
See original GitHub issueWhen making a cross-stack reference in a property override, the cross-stack references do not get processed into an export/import pair, and result in an invalid template.
This is effectively preventing usage of property overrides to work around the deficiencies of the VPC
class if the VPC instance is in a separate stack.
Reproduction Steps
I’ve created a simple (enough) repro of this issue here: RomainMuller/cdk-cross-stack-bug:test/cdk-cross-stack-bug.test.ts
Environment
- CLI Version : 1.51.0
- Framework Version: 1.51.0
- Node.js Version: v14.5.0
- OS : MacOS
- Language (Version): all
This is 🐛 Bug Report
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:6 (1 by maintainers)
Top Results From Across the Web
CDK tips, part 3 – how to unblock cross-stack references
All you have to do is pass an object from one Stack to another, and reference it there. The CDK will generate a...
Read more >Using dynamic references to specify template values
Dynamic references provide a concise, powerful way for you to specify external values stored and managed in other services in your stack templates....
Read more >css - Media Query Styles Not Overriding Original Styles
I can see the style being "applied" when I press F12 and select that element. However, the style itself is crossed out and...
Read more >Limiting Cross-stack References in CDK - Chariot Solutions
In the case of a Lambda triggered by the completion of an ECS task, you don't need to know the complete task definition...
Read more >Autocomplete API - Material UI - MUI
Name Type Default
options * array
renderInput * func
autoComplete bool false
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I encountered this myself in adding a work-around to implement EFS support for an ECS task - I could see this being a frequent issue if anybody needs to utilize the “Escape Hatch” for new features supported by Cloudformation.
Figured it out, you can use
stack.exportValue()
to get resolved reference.