Phillip Simonds
Phillip Simonds
Fixes #123
### Environment * Python version: 3.7.x * schema-enforcer version: 1.1.2 ### Issue Ansible v2.10.7 is an optional dependency of schema-enforcer v1.1.2. This is vulnerable to CVE-2021-3583 and should be patched.
### Environment * Python version: 3.7.9 * schema-enforcer version: 0.1.1 ### Proposed Functionality Schema enforcer currently calls sys.exit(1) after an error occurs, rather than raising an exception which describes the...
### Environment * Python version: 3.7.x+ * schema-enforcer version: 1.0 ### Proposed Functionality Currently, schema enforcer only supports JSONSchema as it's schema language. This feature request proposes adding support for...
### Environment * Python version: 3.7.9 * schema-enforcer version: 1.0.1 ### Proposed Functionality Right now, when two schemas are used to evaluate the same schema file, all checks pass, and...
### Environment * Python version: 3.7.9 * schema-enforcer version: 1.0.1 ### Expected Behavior When `schema-enforcer validate --show-checks` is run and a data file exists at the base path in which...
### Environment * Python version: 3.7.9 * schema-enforcer version: 1.0.1 ### Proposed Functionality Support pulling a JSONSchema definition from a URL ```yaml --- $schema=https://my.url.to/the/schema ``` ### Use Case If schemas...
## Problem Overview Schema-enforcer currently creates Ansible inventory by instantiating a custom `AnsibleInventory` class. This class glues some ansible built-in classes and some custom methods together to create the inventory...
When a data file is mapped to a schema ID which does not exist, rather than exiting with an error code of 1 and printing a failure message to the...
The following need to be updated/written for this issue to be considered resolved: - [x] README.md at root of repo - [x] `docs/configuration.md` - [x] `docs/mapping_schemas.md` - [x] `docs/validate_command.md` -...