-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Linting fails with ansible-lint version >= 6.0.0 #4188
Labels
Comments
It appears that the only way to view the severity is by using ansible-lint's |
mperry2
added a commit
to mperry2/ale
that referenced
this issue
May 8, 2022
ansible-lint 6.0.0 removed the `--parseable-severity`. Use the JSON output in its place. Fixes dense-analysis#4188
mperry2
added a commit
to mperry2/ale
that referenced
this issue
May 8, 2022
ansible-lint 6.0.0 removed the `--parseable-severity` option. Use the JSON output in its place. Fixes dense-analysis#4188
hsanson
pushed a commit
that referenced
this issue
May 9, 2022
ansible-lint 6.0.0 removed the `--parseable-severity` option. Use the JSON output in its place. Fixes #4188
cyyever
pushed a commit
to cyyever/ale
that referenced
this issue
Jul 11, 2022
ansible-lint 6.0.0 removed the `--parseable-severity` option. Use the JSON output in its place. Fixes dense-analysis#4188
cyyever
pushed a commit
to cyyever/ale
that referenced
this issue
Jul 11, 2022
ansible-lint 6.0.0 removed the `--parseable-severity` option. Use the JSON output in its place. Fixes dense-analysis#4188
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Information
VIM version
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Oct 01 2021 01:51:08)
Included patches: 1-2434
Operating System: Debian 11
What went wrong
ansible-lint removed the
--parseable-severity
option in version 6.0.0 (ansible/ansible-lint#1898) which is causing the ALE linter for ansible-lint to fail.Reproducing the bug
:ALEInfo
The text was updated successfully, but these errors were encountered: