The skip list has disabled no-jinja-nesting since 2022. ansible-lint
v6.6.0 replaced that rule with jinja[invalid], and ansible-lint still
maps the old name to it, so the skip now turns off the Jinja syntax
check for tasks in roles/custom, the only path the ansible-lint hook
lints. Remove the skip.
roles/custom has no jinja[invalid] findings at this commit. A syntax
error planted in a task's arguments is reported with this change and
not without it; one planted in a role's defaults file is not reported
either way.
Reference: https://ansible-lint.readthedocs.io/en/latest/default_rules/#var-naming
We don't really fix these, but just suppress them,
because they're like that intentionally.
We try to name variables in a way that is consistent with the
configuration key they control. If the upstream component uses
camelCase, we also need to include camelCase in the variable name.
QEDeDandSlavi Pantaleev
Suguru Hirahara