You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using uppercase variables in tasks are reported as `var-naming: Task defines variables within 'vars' section that violates variable naming standards´. The same variables for blocks are not reported.
Failed to guess project directory using git:
WARNING Overriding detected file kind 'yaml' with 'playbook' for given positional argument: test.yml
WARNING Listing 1 violation(s) that are fatal
var-naming: Task defines variables within 'vars' section that violates variable naming standards
test.yml:12 Task/Handler: foo2
You can skip specific rules or tags by adding them to your configuration file:
# .ansible-lint
warn_list: # or 'skip_list' to silence them completely
- experimental # all rules tagged as experimental
Finished with 0 failure(s), 1 warning(s) on 1 files.
Desired Behavior
The issue needs to be reported for the task and the block.
Actual Behavior
The issue is only reported for the task, but not the block.
The text was updated successfully, but these errors were encountered:
Summary
Using uppercase variables in tasks are reported as `var-naming: Task defines variables within 'vars' section that violates variable naming standards´. The same variables for blocks are not reported.
Issue Type
Ansible and Ansible Lint details
OS / ENVIRONMENT
Fedora 35
STEPS TO REPRODUCE
Using ansible-lint on this playbook
results in
Desired Behavior
The issue needs to be reported for the task and the block.
Actual Behavior
The issue is only reported for the task, but not the block.
The text was updated successfully, but these errors were encountered: