Also, ACD is no longer ACD, it is "ansible" and ansible that used to be "ansible" is ansible-base.

This is something that is currently breaking in Ansible 2.9 and below, but is fixed in ansible-base/2.10: ansible/ansible#69307

So basically, have two collections (with different names), and both collections have a role with the same role name. Have each role maybe write a different-named file to the filesystem, then in the playbook, have an assert that fails if both of those files don't exist.

Add a test that runs playbook using Molecule on [current version of Ansible].

As of February, the status of ACD / 'what is installed with pip install ansible as of 2.10' has been:

Please note that ACD is still currently in development and not available for testing yet at this time.

(Additionally, ansible-base is not yet installable either... but I could install devel.)

The main goal of this repository is to start testing what kind of modifications a playbook that works in Ansible 2.9 and earlier would need to run in ACD (hopefully, none).

When looking at some other examples relating to the tombstoning PR (see #7), I realized I should also add a plugin that imports from a module_util that was moved out of ansible core, to make sure that redirection is working correctly for those who have custom Jinja filters or plugins.

The first playbook / use case is something that I have a lot of in Ansible 2.9 and earlier—use some galaxy content, a local role, some modules in ansible core that are not core-maintained...

• Has a local ('standalone') role that is not part of Ansible Galaxy and uses modules that are in the community.general collection as of Ansible 2.10.
• Has a role or two installed from Ansible Galaxy (like geerlingguy.mysql)
• Uses content from a collection on Ansible Galaxy (like k8s_exec module in community.kubernetes — a module that's not in core 2.9)
• Has a requirements.yml file to install said role(s) and collection(s) (ideally with one command to install all dependencies—currently it's impossible to do this even in 2.9)

When attempting to run the same-named role in a 2nd collection, the ansible-stable test is failing in this playbook's CI; there's a bug open for this: ansible/ansible#69307 — note that the bug was fixed in devel but has not been backported to 2.9.

In #3 I got ACD installing (a very preliminary pre-build) and am using that to test the 2.9-era playbook (making sure modules and roles still work correctly).

However, ACD is currently failing because it needs this (ansible/ansible#67684) tombstoning/redirection PR in place to resolve the modules to the proper locations.

I'm not sure if that PR works or not, yet, but having a test playbook like this one should ensure there's some form of CI against it using an external playbook. I just need to figure out how to get that PR integrated with what I'm building for ACD...

Currently the ACD build fails with:

ERROR! couldn't resolve module/action 'docker_container'. This often indicates a misspelling, missing collection, or incorrect module path.

The error appears to be in '/opt/hostedtoolcache/Python/3.7.6/x64/lib/python3.7/site-packages/molecule/provisioner/ansible/playbooks/docker/destroy.yml': line 8, column 7, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

  tasks:
    - name: Destroy molecule instance(s)
      ^ here

After working through #1, the local role I'm running is running into an issue where Ansible can't find the module that I used successfully in the playbook when the same task is copied into a role I created locally using ansible-galaxy init replay in the roles/ directory:

TASK [include_role : replay] ***************************************************
ERROR! couldn't resolve module/action 'k8s_exec'. This often indicates a misspelling, missing collection, or incorrect module path.

The error appears to be in '/Users/jgeerling/Development/GitHub/ansible-content-testing/roles/replay/tasks/main.yml': line 10, column 3, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:


- name: Test the k8s_exec module from the collection (in replay).
  ^ here

This seems to be me running into this annoying issue again: ansible/ansible#68198

See title.