Check ImportValue refers to a real import
See original GitHub issuecfn-lint version: (cfn-lint --version
) 0.6.1
Description of issue.
Made a mistake in a template typo’ing an import name, had to go through a full deploy/error/fix cycle to figure this out. It would be nice if cfn-lint would check all my (non-templated) imports actually exist on my account, although this might be disruptive when working on multiple templates at once and one imports the export of another.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Check ImportValue refers to a real import · Issue #326 - GitHub
Description of issue. Made a mistake in a template typo'ing an import name, had to go through a full deploy/error/fix cycle to figure...
Read more >Fn::ImportValue - AWS CloudFormation
You can use the intrinsic function Fn::ImportValue to import only values that have been exported within the same region. For outputs, the value...
Read more >Fn::ImportValue - Amazon CloudFormation - 亚马逊云科技
You can use the intrinsic function Fn::ImportValue to import only values that have been exported within the same region. For outputs, the value...
Read more >how to use ImportValue in parameters? - Stack Overflow
One way of doing this is to use a condition: Parameters: MyValue: Type: String Value: '' Conditions: MyValueExists: !Not [ !
Read more >How to export and import stack output values in CDK?
To import those values, we use the `Fn::ImportValue` function in the template for the other stacks. In the context of CDK, a CDK...
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 Free
Top 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
At this time, this enhancement collides with the design goal of keeping the linter as self-contained as possible. That’s not to stop you from writing it as a custom rule though and integrating it locally.
What makes it more complex is that the linter is completely “standalone”. It does not need AWS tools, Boto or any actions. It’s a static file analysis tool. Adding a feature to actually connect to AWS accounts is not that “easy”.