Address the following warning:
```
ERROR: Found 1 shellcheck issue(s) which need to be resolved:
ERROR: ci/incluster_integration.sh:16:7: SC2236: Use -n instead of ! -z.
```
* 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
* 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
A recent change in Ansible
(42da480721)
added a has_action field to the json output of ansible-doc. This started
causing the downstream sanity checks to fail.
* doc fragments workaround for downstream
Signed-off-by: Adam Miller <admiller@redhat.com>
* make shellcheck happy
Signed-off-by: Adam Miller <admiller@redhat.com>
* fix collection location for downstream doc fragment resolution
Signed-off-by: Adam Miller <admiller@redhat.com>
* do things in the correct order
Signed-off-by: Adam Miller <admiller@redhat.com>
* add ANSIBLE_COLLECTIONS_PATH to ansible-doc for downstream
Signed-off-by: Adam Miller <admiller@redhat.com>
* remove elements of the json dump that aren't valid for DOCUMENTATION
Signed-off-by: Adam Miller <admiller@redhat.com>
* Add fix for Ansible 2.9
Signed-off-by: Abhijeet Kasurde <akasurde@redhat.com>
* Update ci/downstream.sh
Co-authored-by: Abhijeet Kasurde <akasurde@redhat.com>
Co-authored-by: Jeff Geerling <geerlingguy@mac.com>
* Fix ci/downstream.sh docs "branding"
Signed-off-by: Adam Miller <admiller@redhat.com>
* fix CHANGELOG.rst title overline length
Signed-off-by: Adam Miller <admiller@redhat.com>
* If deploymentconfigs are configured to trigger on image stream updates don't try to replace image field
* First pass at parsing the trigger annotation
* First draft of IS idempotence tests
* Found even more not idempotent stuff
* Separate handling of annotation and dc spec
* handle malformed annotations
* refactor incluster integration test to catch last flake
* Add proper DNS01 regex for container names
* fix broken conditional for trigger annotations
* Handle namespace field that is added to trigger
* deduplicate shared code
* Set namespace in incluster script
* Give high permissions to test pod
* Still working on permissions issues in prow
* Fix inventory test
* add namespace to watch
* run in default namespace
* fix recursive call
* Fix ansible collection path for downstream test
* Clone the proper ansible collection
* add downstream build scripts
Signed-off-by: Adam Miller <admiller@redhat.com>
* this works locally ... let's see if it does in GitHub Actions
Signed-off-by: Adam Miller <admiller@redhat.com>
* it's running now, but something unrelated seems to be failing
Signed-off-by: Adam Miller <admiller@redhat.com>
* maybe this will work
Signed-off-by: Adam Miller <admiller@redhat.com>
* come on GA, work with me here
Signed-off-by: Adam Miller <admiller@redhat.com>
* lets try this a different way
Signed-off-by: Adam Miller <admiller@redhat.com>
* maybe this?
Signed-off-by: Adam Miller <admiller@redhat.com>
* alright, let's do it all without being so disruptive to the Makefile and GA
Signed-off-by: Adam Miller <admiller@redhat.com>
* I think this fixes prow
Signed-off-by: Adam Miller <admiller@redhat.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
