cyhy_amis/.yamllint at develop · RAMCCs4/cyhy_amis · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
---
# Based on ansible-lint config
extends: default

rules:
  braces:
    # Do not allow non-empty flow mappings
    forbid: non-empty
    # Allow up to one space inside braces. This is required for Ansible compatibility.
    max-spaces-inside: 1
    level: error

  brackets:
    # Do not allow non-empty flow sequences
    forbid: non-empty
    max-spaces-inside: 1
    level: error

  colons:
    max-spaces-after: -1
    level: error

  commas:
    max-spaces-after: -1
    level: error

  comments:
    # Ensure that inline comments have at least one space before the preceding content.
    # This is required for Ansible compatibility.
    min-spaces-from-content: 1

  # 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

  document-start: disable

  empty-lines:
    max: 3
    level: error

  hyphens:
    level: error

  indentation:
    # Ensure that block sequences inside of a mapping are indented
    indent-sequences: true
    # Enforce a specific number of spaces
    spaces: 2

  key-duplicates: enable

  # 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
    # Allows a 10% overage from the default limit of 80
    max: 88

  new-line-at-end-of-file: disable

  new-lines:
    type: unix

  # Using anything other than strings to express octal values can lead to unexpected
  # and potentially unsafe behavior. Ansible strongly recommends against such practices
  # and these rules are needed for Ansible compatibility. Please see the following for
  # more information:
  # https://ansible.readthedocs.io/projects/lint/rules/risky-octal/
  octal-values:
    # Do not allow explicit octal values (those beginning with a leading 0o).
    forbid-explicit-octal: true
    # Do not allow implicit octal values (those beginning with a leading 0).
    forbid-implicit-octal: true

  quoted-strings:
    # Allow disallowed quotes (single quotes) for strings that contain allowed quotes
    # (double quotes).
    allow-quoted-quotes: true
    # Apply these rules to keys in mappings as well
    check-keys: true
    # We prefer double quotes for strings when they are needed
    quote-type: double
    # Only require quotes when they are necessary for proper processing
    required: only-when-needed

  trailing-spaces: disable