csa/devops/ansible-patches/openshift.git - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Age	Files	Lines
...
* \|	Do not require python-six via openshift_facts	Rodolfo Carvalho	2017-03-20	1	-6/+3
\|/ \| \| \| \| \| \| \| \| \| \| \| \|	It turns out the code in roles/openshift_health_checker/openshift_checks/__init__.py had a mistake in the import statement, and not the case that `add_metaclass` is not available in the embedded `six` from `ansible.module_utils`. The fix is to correct the import and do not require python-six to be installed on target hosts. Note: now that we have some unit tests in the role, errors like that would have been caught.
*	Add unit tests for existing health checks	Rodolfo Carvalho	2017-03-17	3	-1/+47
\|
*	Revert module_utils six for openshift_health_checker	Jason DeTiberus	2017-03-13	1	-1/+3
\| \| \| \| \|	Embedded version of six in Ansible 2.2.1 does not support add_metaclass, so revert to using python-six.
*	Use ansible.compat.six where possible	Jason DeTiberus	2017-03-09	1	-2/+5
\|
*	Use six from ansible.module_utils for remote hosts	Jason DeTiberus	2017-03-09	1	-3/+2
\|
*	Renamed NotContainerized to NotContainerizedMixin and dropped no-member	Steve Milner	2017-02-22	5	-12/+10
\|
*	Fix typo	Rodolfo Carvalho	2017-02-21	1	-1/+1
\|
*	Do not hard code package names	Rodolfo Carvalho	2017-02-10	2	-14/+17
\|
*	Refactor code to access values from task_vars	Rodolfo Carvalho	2017-02-10	4	-17/+25
\|
*	Document how to create new checks	Rodolfo Carvalho	2017-02-10	2	-0/+36
\|
*	Introduce tag notation for checks	Rodolfo Carvalho	2017-02-10	5	-1/+34
\| \| \| \|	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	11	-0/+619
	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.