-
Notifications
You must be signed in to change notification settings - Fork 592
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
Issue parsing colons on Linux #1984
Comments
Interesting, wasn't able to reproduce on Ubuntu either. Wonder if it's specific to Amazon Linux |
Just for reference we did find some oddities in Alpine systems too. #666 not sure if this is related or not but its worth noting we try to use the C parsers when available for speed reasons. |
Possible references that we need to investigate. We need to start by knowing if it ends up using the Cparser or not and then what version of that library it may be using. yaml/libyaml#28 and yaml/pyyaml#45 |
Seems like the most recent release has resolved this |
maybe #1992? |
cfn-lint version: 0.48.2 (
cfn-lint --version
)Description of issue.
When I lint this file on my Mac using 0.48.2, I get no errors. When the same file is linted using 0.48.2 in CodeBuild (aws/codebuild/amazonlinux2-x86_64-standard:3.0) it returns:
The offending line is:
- { Key: prx:meta:tagging-version, Value: "2021-04-07" }
CloudFormation has no issues with the code (it creates those tags as expected). Quoting the values makes the linter happy, even in CodeBuild, but it shouldn't be necessary, and since the results are inconsistent between platforms it's hard/annoying to catch them during development. Also it's a false positive, so it's mainly just noise during CI.
The text was updated successfully, but these errors were encountered: