r3pek/log4j-affected-db
1
0
Fork 0
mirror of https://github.com/cisagov/log4j-affected-db.git synced 2024-11-22 16:40:48 +00:00
Code Releases Activity

Update ansible-lint configuration

Browse source 
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.
This commit is contained in:
Nicholas McDonnell 2021-10-27 21:53:10 -04:00
parent 6a10135f81
commit 4b912fe7ca
No known key found for this signature in database
GPG key ID: 7994ADE2A56BE5D1
1 changed files with 6 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
.ansible-lint
View file

@ -13,7 +13,10 @@ exclude_paths:
- .cache - .cache
# Seems wise to ignore this too # Seems wise to ignore this too
- .github - .github
# These two are Molecule configuration files, not Ansible playbooks kinds:
- molecule/default/molecule-no-systemd.yml # This will force our systemd specific molecule configurations to be treated
- molecule/default/molecule-with-systemd.yml # 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 use_default_rules: true