From 8a7dd50b6b9533162a431dfbae48510a777fa93c Mon Sep 17 00:00:00 2001 From: "James E. Blair" Date: Wed, 18 Sep 2024 09:04:32 -0700 Subject: [PATCH] Ignore some recent ansible-list warnings We don't need to name every play; in the Zuul context, they are usually pretty self-evident. It might be nice, but it doesn't seem necessary to require it. We really don't need to care about using upper or lower case. The key-order seems very arbitrary and counterproductive to make all our developers memorize someone else's arbitrary preference for ordering. Change-Id: I49455b6946d5d9b6bffd58420fea586ecc6c5f80 --- .ansible-lint | 3 +++ 1 file changed, 3 insertions(+) diff --git a/.ansible-lint b/.ansible-lint index 026ee3a50..3a49204da 100644 --- a/.ansible-lint +++ b/.ansible-lint @@ -9,6 +9,9 @@ skip_list: - fqcn # similar to above - risky-file-permissions # It would probably also good to enforce this if someone wants to look at them - schema # This is a stricter form of schema per https://github.com/ansible/schemas. might also be good if someone has motivation? + - key-order # This suggests an arbitrary ordering of keys which means our developers would need to memorize someone's personal preference + - name[play] # We have no objection to naming plays, but because of all of our short job playbooks, there are a *lot* of them that are pretty self-evident in the Zuul context, so it doesn't seem necessary. + - name[casing] # We should use proper capitalization, but this is too nit-picky to waste time on # NOTE(ianw) After following the jinja formatting extensions in # ansible-lint for a few releases, this does not seem to be