Fix "couldn't resolve module/action 'k8s_exec'" about ansible-content-testing HOT 2 CLOSED

Apparently that issue's also been locked in addition to closed, so... I guess this will never change and I'll need to add an extra step into the process for every role I create that uses any modules that aren't in Ansible core.

Grr.

from ansible-content-testing.

So before the steps were:

ansible-galaxy init myrole
[copy tasks into new role main/tasks.yml]
[run playbook]

And copy and paste tasks from playbook into myrole.

Now steps are:

ansible-galaxy init myrole
[copy tasks into new role main/tasks.yml]
[run playbook]
<playbook run breaks>
[figure out which tasks I just copied and pasted require which collections in the playbook]
nano myrole/metadata/main.yml
[edit to add `collections:` stuff from playbook]
[save file]
[run playbooks]

And finally the tasks in the role should work the same as they did in the playbook.

Now, for many of my playbooks, where I may have multiple collections defined, I will have to also figure out which ones to add to my role meta file, since I may have one or more on the playbook level that are not needed in the role.

This is a lot more mental burden.

from ansible-content-testing.