Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | skip PackageAvailability check if not yum | juanvallejo | 2017-04-11 | 1 | -0/+4 |
| | |||||
* | Rename module_executor -> execute_module | Rodolfo Carvalho | 2017-03-28 | 1 | -1/+1 |
| | | | | | | | | It is a function/callable, the name should imply action, should be a verb and not a noun. Keep supporting the old name while we have PRs in-flight that use the old name. | ||||
* | Renamed NotContainerized to NotContainerizedMixin and dropped no-member | Steve Milner | 2017-02-22 | 1 | -2/+2 |
| | |||||
* | Refactor code to access values from task_vars | Rodolfo Carvalho | 2017-02-10 | 1 | -7/+3 |
| | |||||
* | Introduce tag notation for checks | Rodolfo Carvalho | 2017-02-10 | 1 | -0/+1 |
| | | | | This allows us to refer to a group of checks using a single handle. | ||||
* | Replace multi-role checks with action plugin | Rodolfo Carvalho | 2017-02-10 | 1 | -0/+69 |
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. |