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
Perform Ansible syntax checking on linted playbooks #787
Labels
Comments
ssbarnea
added a commit
that referenced
this issue
Aug 13, 2020
Fixes issue where users feed task/var files to the linter when in reality it accepts only playbooks and roles. The linter reported the task files as playbooks but silently failed to lint them and passed. From now, any argument that is of playbook type will generate specific errors if ansible syntax-check fails to process it. If you still want to use old behavior you can still add 902 to skiplist. That is WIP and not working, please comment only on architectural parts and ignore minor details (it will be cleaned after). Fixes: #787
ssbarnea
added a commit
that referenced
this issue
Aug 13, 2020
Fixes issue where users feed task/var files to the linter when in reality it accepts only playbooks and roles. The linter reported the task files as playbooks but silently failed to lint them and passed. From now, any argument that is of playbook type will generate specific errors if ansible syntax-check fails to process it. If you still want to use old behavior you can still add 902 to skiplist. That is WIP and not working, please comment only on architectural parts and ignore minor details (it will be cleaned after). Fixes: #787
ssbarnea
added a commit
that referenced
this issue
Aug 13, 2020
Fixes issue where users feed task/var files to the linter when in reality it accepts only playbooks and roles. The linter reported the task files as playbooks but silently failed to lint them and passed. From now, any argument that is of playbook type will generate specific errors if ansible syntax-check fails to process it. If you still want to use old behavior you can still add 902 to skiplist. That is WIP and not working, please comment only on architectural parts and ignore minor details (it will be cleaned after). Fixes: #787
ssbarnea
added a commit
that referenced
this issue
Aug 13, 2020
Fixes issue where users feed task/var files to the linter when in reality it accepts only playbooks and roles. The linter reported the task files as playbooks but silently failed to lint them and passed. Fixes: #787
ssbarnea
changed the title
feature: make use of PlaybookExecutor in order to include Ansible Syntax Check
Perform Ansible syntax checking on linted playbooks
Aug 13, 2020
ssbarnea
added a commit
that referenced
this issue
Aug 14, 2020
Fixes issue where users feed task/var files to the linter when in reality it accepts only playbooks and roles. The linter reported the task files as playbooks but silently failed to lint them and passed. Fixes: #787
ssbarnea
added a commit
that referenced
this issue
Dec 31, 2020
ssbarnea
added a commit
that referenced
this issue
Dec 31, 2020
ssbarnea
added a commit
that referenced
this issue
Dec 31, 2020
ssbarnea
added a commit
that referenced
this issue
Dec 31, 2020
ssbarnea
added a commit
that referenced
this issue
Dec 31, 2020
ssbarnea
added a commit
that referenced
this issue
Jan 1, 2021
ssbarnea
added a commit
that referenced
this issue
Jan 4, 2021
ssbarnea
added a commit
that referenced
this issue
Jan 4, 2021
ssbarnea
added a commit
that referenced
this issue
Jan 5, 2021
ssbarnea
added a commit
that referenced
this issue
Jan 5, 2021
ssbarnea
added a commit
that referenced
this issue
Jan 6, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In order to include results from
ansible --syntax-check
we should make use ofPlaybookExecutor.run()
so users of the linter would not have to also run ansible check on the files.A good start would be to identify a problem that is reported by ansible own syntax check but not by ansible-lint
The text was updated successfully, but these errors were encountered: