This was the most elegant way I could think of to resolve #220.
This will create a directory at WORKDIR/.local/lib/python3.9/site-packages. With the default WORKDIR, it would be /runner/.local/lib/python3.9/site-packages. Which once python is launched under the runner user, the new path is included in the python paths. Then if a python module is installed during a playbook to that path, it is accessible by both modules and lookups.
This was the most elegant way I could think of to resolve #220.
This will create a directory at
WORKDIR/.local/lib/python3.9/site-packages. With the default WORKDIR, it would be/runner/.local/lib/python3.9/site-packages. Which once python is launched under the runner user, the new path is included in the python paths. Then if a python module is installed during a playbook to that path, it is accessible by both modules and lookups.