Stop requiring plugin dirs to have init for mazer list --content.
The is_plugin_dir() method used by installed_content_item_db
which is used by 'mazer list' was excluding potential content_items
if their plugin dir did not contain an init.py.
Before this change, 'mazer list --content' would not list info
about any content items that did not have an init.py.
Remove the the init.py check so all plugin dirs are considered
content items so list does the right thing now.
ISSUE TYPE
Bugfix Pull Request
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
SUMMARY
Stop requiring plugin dirs to have init for
mazer list --content.The is_plugin_dir() method used by installed_content_item_db which is used by 'mazer list' was excluding potential content_items if their plugin dir did not contain an init.py.
Before this change, 'mazer list --content' would not list info about any content items that did not have an init.py.
Remove the the init.py check so all plugin dirs are considered content items so list does the right thing now.
ISSUE TYPE
MAZER VERSION