Recommended practices for all elements of automation using Ansible, starting with collections and roles, continuing with playbooks, inventories and plug-ins... These good practices are planned to be used by all Red Hat teams interested but can of course be used by others.
268
stars
66
forks
source link
Avoid ansible-lint conflict related to prefix on ansible roles #96
Current example of - name: sub | some task description is not passing linting because it should look like - name: sub | Some task description.
The linter does know about the prefix for roles, but also has a rule that asks for all descriptions/titles to be capitalized, in that particular case, that means that first alpha letter after pipe separator should be capitalized.
Please read https://github.com/ansible/ansible-lint/issues/3186 and consider updating the recomandation for prefixing with an example that does not conflict with linter asking for capitalization.
Current example of
- name: sub | some task descriptionis not passing linting because it should look like- name: sub | Some task description.The linter does know about the prefix for roles, but also has a rule that asks for all descriptions/titles to be capitalized, in that particular case, that means that first alpha letter after pipe separator should be capitalized.