mirror of
https://github.com/cisagov/log4j-affected-db.git
synced 2024-11-22 08:30:48 +00:00
4b912fe7ca
Instead of excluding molecule configurations for systemd individually we instead direct ansible-lint to process any of these configurations in scenario directories as plain yaml files. This mirrors how ansible-lint handles `molecule.yml` files in scenario directories by default.
23 lines
837 B
Text
23 lines
837 B
Text
---
|
|
# See https://ansible-lint.readthedocs.io/en/latest/configuring.html
|
|
# for a list of the configuration elements that can exist in this
|
|
# file.
|
|
enable_list:
|
|
# Useful checks that one must opt-into. See here for more details:
|
|
# https://ansible-lint.readthedocs.io/en/latest/rules.html
|
|
- fcqn-builtins
|
|
- no-log-password
|
|
- no-same-owner
|
|
exclude_paths:
|
|
# This exclusion is implicit, unless exclude_paths is defined
|
|
- .cache
|
|
# Seems wise to ignore this too
|
|
- .github
|
|
kinds:
|
|
# This will force our systemd specific molecule configurations to be treated
|
|
# as plain yaml files by ansible-lint. This mirrors the default kind
|
|
# configuration in ansible-lint for molecule configurations:
|
|
# yaml: "**/molecule/*/{base,molecule}.{yaml,yml}"
|
|
- yaml: "**/molecule/*/molecule-{no,with}-systemd.yml"
|
|
use_default_rules: true
|