-
-
Notifications
You must be signed in to change notification settings - Fork 164
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
invalid yaml #358
Comments
|
here's diffs another and the last one |
|
actually, all the yaml files are missing the header line just install yamllint (pip install yamllint) and test them all |
|
@speculatrix in the future, can you submit pull requests for your fixes? Thanks. |
|
Hi, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
hello
we test all the files in our puppet files repository with our CI/CD system
yamllint shows that the yaml files are missing the "---" headings, and a problem with a blank line
/tmp/build/32643510/devel-branch/environments/production/modules/gitlab/data/family/RedHat.yaml
2:1 warning missing document start "---" (document-start)
22:1 error too many blank lines (1 > 0) (empty-lines)
yamllint found error in /tmp/build/32643510/devel-branch/environments/production/modules/gitlab/data/family/RedHat.yaml when using config /tmp/build/32643510/ci-scripts/ci/yamllint-config.yaml
===============================================================================
Checking /tmp/build/32643510/devel-branch/environments/production/modules/gitlab/data/family/RedHat/6.yaml
/tmp/build/32643510/devel-branch/environments/production/modules/gitlab/data/family/RedHat/6.yaml
1:1 warning missing document start "---" (document-start)
===============================================================================
Checking /tmp/build/32643510/devel-branch/environments/production/modules/gitlab/data/os/Ubuntu.yaml
/tmp/build/32643510/devel-branch/environments/production/modules/gitlab/data/os/Ubuntu.yaml
1:1 warning missing document start "---" (document-start)
The text was updated successfully, but these errors were encountered: