From 21a68f461cf04ee5009c22e6311afdfdeff6f0fe Mon Sep 17 00:00:00 2001
From: Nicholas McDonnell <50747025+mcdonnnj@users.noreply.github.com>
Date: Wed, 7 Sep 2022 13:35:44 -0400
Subject: [PATCH 1/2] Enable the allow-non-breakable-inline-mappings rule for
 yamllint

---
 .yamllint | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/.yamllint b/.yamllint
index 76a1cce..b5b302f 100644
--- a/.yamllint
+++ b/.yamllint
@@ -8,6 +8,14 @@ rules:
   # this behavior.
   comments-indentation: disable
 
+  # yamllint does not allow inline mappings that exceed the line length by
+  # default. There are many scenarios where the inline mapping may be a key,
+  # hash, or other long value that would exceed the line length but cannot
+  # reasonably be broken across lines.
+  line-length:
+    # This rule implies the allow-non-breakable-words rule
+    allow-non-breakable-inline-mappings: true
+
   # yamllint doesn't like when we use yes and no for true and false,
   # but that's pretty standard in Ansible.
   truthy: disable

From 3547c4f28d98a0e08582f5cf02e53d102a9e5dac Mon Sep 17 00:00:00 2001
From: Nicholas McDonnell <50747025+mcdonnnj@users.noreply.github.com>
Date: Wed, 7 Sep 2022 13:37:21 -0400
Subject: [PATCH 2/2] Increase the maximum line length in the yamllint
 configuration

Increase the line length maximum from the default of 80 to 88. This 10%
increase mirrors the line length allowed in other linter configurations
such as black.
---
 .yamllint | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/.yamllint b/.yamllint
index b5b302f..8f4e6bf 100644
--- a/.yamllint
+++ b/.yamllint
@@ -15,7 +15,8 @@ rules:
   line-length:
     # This rule implies the allow-non-breakable-words rule
     allow-non-breakable-inline-mappings: true
-
+    # Allows a 10% overage from the default limit of 80
+    max: 88
   # yamllint doesn't like when we use yes and no for true and false,
   # but that's pretty standard in Ansible.
   truthy: disable