The goal here is to limit the suppressions in .ansible-lint, .yamllint.yml,
and in-line in the file to a bare minimum, so that we can pass various
gating tests for Ansible Galaxy and Automation Hub, both now, and into
the foreseeable future.
In addition - putting suppressions into .ansible-lint and .yamllint.yml
is problematic:
applies to all files in role - suppressions should be as local as
possible
difficult to "merge" all of the .ansible-lint and .yamllint.yml from
all of the roles when we convert to collection - better to have the
suppressions in the files to which they apply
The goal here is to limit the suppressions in .ansible-lint, .yamllint.yml, and in-line in the file to a bare minimum, so that we can pass various gating tests for Ansible Galaxy and Automation Hub, both now, and into the foreseeable future. In addition - putting suppressions into .ansible-lint and .yamllint.yml is problematic:
For reference about ansible-lint and why these items are being flagged, see https://ansible-lint.readthedocs.io/philosophy/ And see also the recommended practices style guide https://github.com/redhat-cop/automation-good-practices/tree/main/coding_style
true
/false
instead ofyes
/no
---