* Enable turbo mode
This enables turbo mode (default is off) for the modules in this
collection that use the client from the kubernetes.core collection.
* Add changelog fragment
* Fix broken links for downstream collection
The links to the repo on Automation Hub are broken for the downstream
collection. This skips the replacement step for galaxy.yml.
* Add changelog fragment
* Update to work with k8s 2.0
This makes the necessary changes to get the collection working with
kubernetes.core 2.0. The biggest changes here will be switching from the
openshift client to the kubernetes client, and dropping Python 2
support.
* Install kubernetes not openshift
* Add changelog fragment
* Clean up CI build
There were a few problems with the existing build process, such as, the
python version not being passed during sanity tests and versions being
hard coded elsewhere. This change ensures that each test scenario gets
the correct parameters passed through. It also generally cleans up the
process for building the test environment to let ansible-galaxy do its
thing. This will make sure the correct version of dependencies get
installed.
* Add changelog fragment
* Removed old changelog fragment files
* Updated configuration to remove old fragment files
on release
Signed-off-by: Abhijeet Kasurde <akasurde@redhat.com>
* 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
* Fix sanity failure
This fixes a sanity test failure for newer versions of ansible-test. It
was falsely flagging the key parameter for TLS configuration as
sensitive. This parameter is just the path to a key file.
* Restrict molecule version
This is needed to address a breaking change in molecule 3.3.0.
* Add changelog fragment
* Restrict kubernetes.core dependency version
In order to better coordinate releases between this collection and the
kubernetes.core collection we need to use a more restrictive dependency
version range.
* Add changelog fragment
* 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.
