Robert Kaussow
2df48598ec
BREAKING CHANGE: The option to define a `Standards` version has been removed. Every new rule that is added on upcoming releases is activated by default and will also create errors if triggered. The behavior of rules can be controlled by the existing `rules.exclude_filter` or `rules.warning_filter` options. BREAKING CHANGE: The option `rules.buildin` has been renamed to `rules.builtin`. BREAKING CHANGE: The option `rules.standards` has been renamed to `rules.dir`. BREAKING CHANGE: The option `rules.filter` has been renamed to `rules.include_filter`.
1.1 KiB
| title |
|---|
| CLI options |
You can get all available CLI options by running ansible-later --help:
{{< highlight Shell "linenos=table" >}} $ ansible-later --help usage: ansible-later [-h] [-c CONFIG] [-r DIR] [-B] [-i TAGS] [-x TAGS] [-v] [-q] [-V] [rules.files ...]
Validate Ansible files against best practice guideline
positional arguments: rules.files
options: -h, --help show this help message and exit -c CONFIG, --config CONFIG path to configuration file -r DIR, --rules-dir DIR directory of rules -B, --no-builtin disables built-in rules -i TAGS, --include-rules TAGS limit rules to given id/tags -x TAGS, --exclude-rules TAGS exclude rules by given it/tags -v increase log level -q decrease log level -V, --version show program's version number and exit {{< /highlight >}}