-
Notifications
You must be signed in to change notification settings - Fork 636
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
skip_list skips everything #4040
Labels
Comments
Please link to a minimal repository that reproduced the bug. |
I have same problems If you specify this rule, then the number of warnings is 93, if you remove it, then more than 1000. Moreover, if you specify not through .ansible-lint, but through .yamllint.yml, then exactly the desired rule is excluded |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Hi,
I would like to skip a specific tag completely (
var-naming[no-role-prefix]
). I have created the following.ansible-lint
configurationBut now no check is executed at all. Everything seems ok.
If i run ansible-lint without a
.ansible-lint
configuration file, i will get the following ouputIf I skip one tag now, I would have expected the others to still appear. But with the above config I now get the following
But I would still like to have the other messages because I would like to fix them. Just not the one which i want to skip.
Background. I have a collection
namespace.zabbix
and in it several roles (agent, server, proxy, ...). Now my variables have the structurezabbix_ROLE_variable
(e.g.zabbix_agent_port
), but ansible-lint complains about it. (That's ok, it's defined that way). But surely this one check can be ignored somehow.Issue Type
OS / ENVIRONMENT
ansible-lint 6.22.1 using ansible-core:2.16.3 ansible-compat:4.1.11 ruamel-yaml:0.17.40 ruamel-yaml-clib:0.2.8
STEPS TO REPRODUCE
Add a simple
.ansible-lint
configuration withskip_list
Desired Behavior
Only the one check is ignored
Actual Behavior
Everything is ignored
The text was updated successfully, but these errors were encountered: