- delay the loading of external modules when possible
- delay the loading of OKDRawModule and OpenShiftProcess classes
- k8s reuse the design of the kubernetes.core modules
We've got a chicken/egg problem that prevent us from properly
reporting if kubernetes.core is missing. We need args_common to create
the module object. And we need the module object to report the missing
dependency. The dependency is declared in the galaxy.yml file anyway,
the problem should not happen.
Follow up to the recent upgrade of pylint in the devel branch, we've
got a new use-a-generator error in k8s.py:
Use a generator instead 'all(desired.get(key, True) == item.get(key, False) for key in keys)'
This commit disables the error until we've got time to rewrite this
part.
Also, since the older branches still use an ancient version of pylint,
we've got another message saying the error does not exist (yet!).
This commit also adds the right entries in the ignore files.
* Update CI for ansible 2.11
This copies the ignore-2.11.txt to ignore-2.12.txt and makes sure the CI
build tests against ansible 2.11.
* Add changelog fragment
* Initial pass at openshift_process module. Render-only
* fix sanity test
* Add ability to create/delete resources rendered by template
* fix sanity tests
* add more tests and fix .env parser
* Add more tests
* Make multiline parsing work properly
* Add test for creating templates
* Template APIs require namespace to be provided whether or not the template exists
* add docs
* Update plugins/modules/openshift_process.py
Co-authored-by: Timothy Appnel <tima@ansible.com>
Co-authored-by: Timothy Appnel <tima@ansible.com>
* Initial port to molecule
* Get molecule tests to run
* Draw the rest of the owl
* use local dir for storing collection during CI run
* Add dockerfile, install community.kubernetes collection before sanity check
* Add clean step to Makefile
* Get sanity tests working
* Update sanity test to use makefile
* Add ignores for 2.11 so devel passes
* Update description
* Code review
* Add OWNERS file for prow
* Issue #1: Initial effort to lift some content out of the Kubernetes collection.
* Issue #1: Disable integration tests for now, as they're not relevant.
