No way we're fixing 47 of these linting errors which seem unimportant.

This format is too pervasive in our infra code, no way we're fixing all
824 instances. (At least not without a notably increased snack budget.)

We were already ignoring fqcn-builtins which is now an alias for
fqcn[action-core] in ansible-lint 6.8.0. The latter started complaining
about fqcn[action] as well, so just opt out of all fqcn checks.

The "line-length" and "braces" rules are now named "yaml[line-length]"
and "yaml[braces]" respectively.

https://github.com/ansible/ansible-lint/pull/2148

To be determined if we want to implement this rule.

yaml: truthy value should be one of [false, true] (truthy)
yaml: wrong indentation: expected 4 but found 2 (indentation)
yaml: too few spaces before comment (comments)
yaml: missing starting space in comment (comments)
yaml: too many blank lines (1 > 0) (empty-lines)
yaml: too many spaces after colon (colons)
yaml: comment not indented like content (comments-indentation)
yaml: no new line character at the end of file (new-line-at-end-of-file)
load-failure: Failed to load or parse file
parser-error: couldn't resolve module/action 'hosts'. This often indicates a misspelling, missing collection, or incorrect module path.

https://github.com/ansible-community/ansible-lint/issues/953

Frederik Schwan authored 4 years ago and Sven-Hendrik Haase committed 4 years ago

fixes #41

Signed-off-by: Jelle van der Waa <jelle@archlinux.org>