2019-03-11 12:52:57 +00:00
|
|
|
---
|
|
|
|
|
extends: default
|
|
|
|
|
|
|
|
|
|
rules:
|
2022-02-25 13:27:32 +00:00
|
|
|
# yamllint does not like it when you comment out different parts of
|
|
|
|
|
# dictionaries in a list. You can see
|
|
|
|
|
# https://github.com/adrienverge/yamllint/issues/384 for some examples of
|
|
|
|
|
# this behavior.
|
|
|
|
|
comments-indentation: disable
|
|
|
|
|
|
2022-09-07 17:35:44 +00:00
|
|
|
# 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
|
2022-09-07 17:37:21 +00:00
|
|
|
# Allows a 10% overage from the default limit of 80
|
|
|
|
|
max: 88
|
2019-03-11 12:52:57 +00:00
|
|
|
# yamllint doesn't like when we use yes and no for true and false,
|
|
|
|
|
# but that's pretty standard in Ansible.
|
|
|
|
|
truthy: disable
|
