Failure to detect CloudFormation templates
See original GitHub issueI have cfn-lint
installed in my path but any time I’m working on a file I have no linter output and the output log shows only this message repeated for every save:
File 'file:///[elided]/service.yaml is a CFN? false
This happens whether I have it installed using Python 2 or 3, in the path or a separate virtualenv, or with the config cfn-lint path set or not. Is there a better way to get debug output to narrow down the cause?
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Troubleshooting CloudFormation - AWS Documentation
If AWS CloudFormation fails to create, update, or delete your stack, ... However, AWS CloudFormation won't recognize some template changes as an update, ......
Read more >Failure to detect CloudFormation templates · Issue #20 - GitHub
I have cfn-lint installed in my path but any time I'm working on a file I have no linter output and the output...
Read more >10 Solutions to Common CloudFormation Errors - Medium
When creating a CloudFormation that includes Lambda Function resources, you should check whether those Lambdas have Environmental Variables. If ...
Read more >AWS CloudFormation Best Practices - Trend Micro
For example, the template may dictate that your application requires 3 Elastic Cloud Compute (EC2) servers and a specific Identify and Access Management...
Read more >Detecting unmanaged configuration changes to stacks and ...
The stack drift detection operation has failed for at least one resource in the stack. Results will be available for resources on which...
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
yea this has been trick @acdha because we don’t want to lint all yaml or json files that you may open so we use that string to determine if we should/can lint it. I’m open to suggestions here. Maybe we could log something that says we didn’t lint the file because it was missing the version.
We are using the CloudFormation version string within the template to determine if the file should be linted. Your template must containt the following string for the linter to pick it up:
AWSTemplateFormatVersion: ‘2010-09-09’
Does that help?