9e394d24d0
This will give us a nice link to the goaccess reports on the zuul dashboard build pages. Move ansible-lint config into config file As of 4.2.0 we can configure ansible-lint with a config file. It's also apparently now smart enough to only find ansible yaml. Let's see how that goes. Add a fake zuul_return module This should let us fake out ansible-lint without having to install all of zuul. Change-Id: Ib233eb577a8ca2aabfe3a49b2cd823dd4a00bd82
41 lines
1.2 KiB
Plaintext
41 lines
1.2 KiB
Plaintext
parseable: true
|
|
quiet: true
|
|
# ANSIBLE0010: Package installs should not use latest
|
|
# We often deploy latest pip packages
|
|
#
|
|
# 204: Lines < 160
|
|
# Things like keys, script lines, etc exceed this. We have good
|
|
# taste and only use long lines where appropriate.
|
|
#
|
|
# 206: {{var}} should have spaces {{ var }}
|
|
# This rule seems sane, but it appears there's no way to convince
|
|
# ansible-lint perfectly good things that are *not* ansible (like
|
|
# exim configs) in YAML shouldn't have to follow this rule. See
|
|
# https://github.com/ansible/ansible-lint/issues/534; might be able
|
|
# to turn on if fixed.
|
|
#
|
|
# 306: shells with pipes should use pipefail
|
|
# This requires running the shell as /bin/bash. There is a small
|
|
# possibility to hide errors, but we can rely on
|
|
# developers to decide when to explicitly check for failures.
|
|
#
|
|
# 503: tasks that run when "changed" should likely be handlers
|
|
# We can trust reviewers to decide if something should be a
|
|
# generic handler or not.
|
|
skip_list:
|
|
- ANSIBLE0004
|
|
- ANSIBLE0006
|
|
- ANSIBLE0007
|
|
- ANSIBLE0010
|
|
- ANSIBLE0011
|
|
- ANSIBLE0012
|
|
- ANSIBLE0013
|
|
- ANSIBLE0015
|
|
- '204'
|
|
- '206'
|
|
- '304'
|
|
- '306'
|
|
- '503'
|
|
use_default_rules: true
|
|
verbosity: 1
|