Replies: 2 comments
-
I think https://github.com/varac/ansible-lint-testrepo is a good example of this behaviour. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I converted this to a discussion because it is problematic and requires further discussions. Main issue is that it breaks predictive behavior, that any passed file-name is a playbooks. If we implement it as described, it will allow false-positives with yaml files that are no longer playbooks. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Currently if a user tries to lint a .yml file, ansible-lint assumes it is a playbook and then outputs any linter issues. If a the .yml file is actually a tasks file such as
tasks/main.yml
, ansible-lint outputs no issues and the user likely thinks the file was linted succesfully. Discussed in #488.Proposal when calling
ansible-lint *.yml
to check if the format is indeed a playbook format versus tasks file format, and exit with an error code if not a playbook.Beta Was this translation helpful? Give feedback.
All reactions