Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | health checks: configure failure output in playbooks | Luke Meyer | 2017-05-23 | 1 | -43/+64 |
| | | | | | Customized the error summary to depend on the intent of the playbook run. Ensured output makes sense when failures are unrelated to running checks. | ||||
* | Show help on how to disable checks after failure | Rodolfo Carvalho | 2017-05-23 | 1 | -0/+22 |
| | |||||
* | Remove vim configuration from Python files | Rodolfo Carvalho | 2017-05-09 | 1 | -1/+0 |
| | | | | | | | In a project where contributors are free to use whatever editor they want and we have linting tools that verify the proper formatting of Python files, it should not be required to have a vim-specific line in Python files. | ||||
* | preflight checks: improve user output from checks | Luke Meyer | 2017-03-20 | 1 | -10/+24 |
| | |||||
* | Replace multi-role checks with action plugin | Rodolfo Carvalho | 2017-02-10 | 1 | -0/+100 |
This approach should make it easier to add new checks without having to write lots of YAML and doing things against Ansible (e.g. ignore_errors). A single action plugin determines what checks to run per each host, including arguments to the check. A check is implemented as a class with a run method, with the same signature as an action plugin and module, and is normally backed by a regular Ansible module. Each check is implemented as a separate Python file. This allows whoever adds a new check to focus solely in a single Python module, and potentially an Ansible module within library/ too. All checks are automatically loaded, and only active checks that are requested by the playbook get executed. |