Variable checker for ansible playbooks
Project description
ansiblevarchecker
CLI to check what vars are defined / used to find undefined or extra vars not documented.
Based on source for ansible 2.9 and striped down and modified version of jinja2schema.
Known Issues
- Sub attributes of a dictionary are marked as defined if a different sub attribute is set e.g
# Setting
dict:
sub: yay
# Will cause the use of the following undefined var to be marked as defined
{{ dict.undefined }}
-
Setting variables in jinja2 templates are seen as variable usage and will be marked as undefined if they have not been registered outside of the jinja2 template
-
Because of the removed scalar typing (to fix issues with filter discovery and other edge cases), infer-ing assumes all if statements evaluate to a boolean which can fail when actually run. This is out of scope of what avc is meant to do and is expected behavior (aka, test your code before pushing)
-
Python 3.6.x isn't tested and isn't 100% supported due to https://www.python.org/dev/peps/pep-0538/ being introduced min 3.7. 3.6 can still be configured to work with UTF-8 encoding but this package is not tested against 3.6
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Hashes for ansiblevarchecker-0.0.1-py2-none-any.whl
Algorithm | Hash digest | |
---|---|---|
SHA256 | 2e533e952de1241d91229faff05afd4b491fb48cd59cf8b980e540b228de7a40 |
|
MD5 | 9ecd0888881fbf6774e9709474617b8a |
|
BLAKE2b-256 | a307d8d40b11c011e79c6b275810ec5c4f922bb0cc93d5de8f681067fe5c9345 |