Test compatibility with ansible-runner

[AlanCoding]

Test compatibility with ansible-runner

[kdelee]

@AlanCoding what do you think about where that should run? We could run two checks in parallel, one that pip installs ansible-runner from pypi and the other that pip installs it from the devel branch.

Since this is a public repo it would be cool to leverage the github actions.

[AlanCoding]

Both of these projects are set up with Zuul, and someone may want the "Depends-On" syntax to run CI with two branches simultaneously. The question of "where should it run?" strikes me as complicated, and I want to delay that question.

Right now, I want to focus on building out code simultaneously with a pipeline which I can run locally, and productively touches back to documentation and the examples that we know we want.

---

For a starter example:

https://galaxy.ansible.com/awx/awx

Consider the newly introduced tower_schedule_rrule lookup plugin. This depends on the python pytz library. It is unlikely that our container images will have this library by default. It's also possible to test this inside of a playbook, which is important because of how ansible-runner hooks things up. We can test almost all of the AWX Ansible venv python dependencies via ansible-inventory, but if you do that, you use a custom command with runner, and that doesn't hook into the callback plugin or anything like that. This plugin can also be used fully locally, just with some debug task. So this is a good candidate to run a relatively complete integration cycle with.

So that would be a really basic example for testing #22 (which is needs_devel), but would allow hooking up the full pipeline. I want to see RRULE printed into the stdout of an ansible-runner event. Anything short of that won't be a genuine proof of concept.

[AlanCoding]

Test fodder for ^ that scenario

ansible/awx#7474

[AlanCoding]

https://github.com/ansible/ansible-builder/tree/devel/examples now fits the bill to some extent

I've talked over some TODO items with @shanemcd and through my own debugging:

• test 2 collections in same example
• test user's python requirement combined with collection
• [needs devel] test EE definition that does some version of dnf install git, or look into other example
• test relative python requirement in EE definition in nested or complex folders like foo/requirements.txt or ../requirements.txt

[AlanCoding]

Closing after feedback from @kdelee in #56