-
Notifications
You must be signed in to change notification settings - Fork 672
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
meta/argument_specs.yml
in a role is treated as a playbook
#1688
Comments
marking it as meta is wrong, it is a new format the linter does not support yet, just force mapping to "args_spec" there. The string has not yet special meaning but will help us write rules specific for these files. yaml checking will still be performed anyway. |
ok makes sense, should I change this to a feature request? Or open a new feature request? |
Just make a PR to fix that bug and we are good. I think it would be a very good idea to include a sample such file inside examples/ directory (inside one role). I am almost sure that if you add it, at least one test will fail. When you make the fix, the test should start to work again. Than ensures that we do not have a regression in the future. |
…based on argument specification Beginning with ansible version 2.11 role argument validation based on an argument specification was introduced. This specification is defined in the meta/argument_specs.yml file of a role. This change enables the linter to detect this new format and for it to be used in future rules. Fixes: ansible#1688 Signed-off-by: Daniel Ziegenberg <[email protected]>
…based on argument specification Beginning with ansible version 2.11 role argument validation based on an argument specification was introduced. This specification is defined in the meta/argument_specs.yml file of a role. This change enables the linter to detect this new format and for it to be used in future rules. Fixes: ansible#1688 Relates: ansible#1966 Signed-off-by: Daniel Ziegenberg <[email protected]>
…based on argument specification Beginning with ansible version 2.11 role argument validation based on an argument specification was introduced. This specification is defined in the meta/argument_specs.yml file of a role. This change enables the linter to detect this new format and for it to be used in future rules. Fixes: ansible#1688 Relates: ansible#1966 Signed-off-by: Daniel Ziegenberg <[email protected]>
Beginning with ansible version 2.11 role argument validation based on an argument specification was introduced. This specification is defined in the meta/argument_specs.yml file of a role. This change enables the linter to detect this new format and for it to be used in future rules. Fixes: #1688 Relates: #1966 Signed-off-by: Daniel Ziegenberg <[email protected]>
Summary
I'm hitting this issue by way of a vscode extension so I'm having a bit of a hard time determining if it's definitely an issue in
ansible-lint
or not (see tomaciazek/vscode-ansible#19).I'm also hitting #1507 so it's difficult for me to run
ansible-lint
directly with a modern version of Ansible.But the issue I'm seeing is that the
meta/argument_specs.yml
is "failing" with an unexpected internal error while other files in the role are being treated ok. This text is shown the extension's log:I was able to workaround it by adding the following in
.ansible-lint
:I'm unsure if marking it as
meta
is "correct" but it does make the failure go away.Issue Type
Ansible and Ansible Lint details
OS / ENVIRONMENT
Ubuntu 18.04 (WSL2)
STEPS TO REPRODUCE
Desired Behaviour
File is linted correctly.
Actual Behaviour
(in description)
The text was updated successfully, but these errors were encountered: