search

ansible / mazer

Experimental Ansible Galaxy Content Manager
GNU General Public License v3.0
114 stars 18 forks source link

Add ansible_collections to default content_roots #205

Closed alikins closed 5 years ago

alikins commented 5 years ago
SUMMARY

Add ansible_collections to default content_roots

The ansible collection loader requires collection name space dirs are below a 'ansible_collections' directory. 'ansible_collections' ends up being the root of a python namespace package where all of the python code can be referenced (including non python code which can be loaded via pkgutils.get_data()).

So the default install locations (aka, content roots) need to have the 'ansible_collections' subdir added to their path.

This updates all of the config defaults, documentation, and the paths used in tests to include 'ansible_collections'

Note: If you have existing collection namespaces in a dir like ~/.ansible/content/, they will need to be manually moved to ~/.ansible/content/ansible_collections/

See https://github.com/ansible/ansible/pull/52194 for the ansible changes.

ISSUE TYPE
MAZER VERSION
name = mazer
version = 0.3.0
config_file = /home/adrian/.ansible/mazer.yml
uname = Linux, newswoop, 4.18.16-100.fc27.x86_64, #1 SMP Sun Oct 21 09:33:00 UTC 2018, x86_64
executable_location = /home/adrian/venvs/galaxy-cli-py3-2/bin/mazer
python_version = 3.6.6 (default, Jul 19 2018, 16:29:00) [GCC 7.3.1 20180303 (Red Hat 7.3.1-5)]
python_executable = /home/adrian/venvs/galaxy-cli-py3-2/bin/python3.6