-
Notifications
You must be signed in to change notification settings - Fork 597
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
cfn-lint gives an error output even if check empty yaml file #3573
Comments
@kddejong (venv) [root@ip-10-188-224-84 ~]# cfn-lint --version (venv) [root@ip-10-188-224-84 ~]# cat test.yaml test purpose |
Fix is in main but not released. We've been releasing fairly frequently so shouldn't be much longer |
@kddejong (venv) [root@ip-10-188-193-12 ~]# cfn-lint --version test purpose(venv) [root@ip-10-188-193-12 ~]# cfn-lint -t test.yaml |
yes we are getting the error as well even with a defined json file with properties |
CloudFormation Lint Version
1.9.5
What operating system are you using?
AWS Linux
Describe the bug
The new version of cfn-lint gives an error message even if checking the empty yaml file.
The last working version is 0.87.4. Any versions newer than 0.87.4 give the same error message.
Here is the output.
(venv) [root@ip-10-188-193-11 ~]# cfn-lint --version
cfn-lint 1.9.5
(venv) [root@ip-10-188-193-11 ~]# vi test.yaml
(venv) [root@ip-10-188-193-11 ~]# ls
test.yaml venv
(venv) [root@ip-10-188-193-11 ~]# cat test.yaml
test purpose
(venv) [root@ip-10-188-193-11 ~]# cfn-lint -t test.yaml
E0002 Unknown exception while processing rule E1001: "'dict' object has no attribute 'start_mark'"
test.yaml:1:1
Expected behavior
Fix the bug
Reproduction template
(venv) [root@ip-10-188-193-11 ~]# cfn-lint --version
cfn-lint 1.9.5
(venv) [root@ip-10-188-193-11 ~]# vi test.yaml
(venv) [root@ip-10-188-193-11 ~]# ls
test.yaml venv
(venv) [root@ip-10-188-193-11 ~]# cat test.yaml
test purpose
(venv) [root@ip-10-188-193-11 ~]# cfn-lint -t test.yaml
E0002 Unknown exception while processing rule E1001: "'dict' object has no attribute 'start_mark'"
test.yaml:1:1
The text was updated successfully, but these errors were encountered: