This result with following symlink:
~/.ansible/collections/ansible_collections/inverse_inc/ansible/
but my collection has name packetfence mentioned in ansible-packetfence/ansible/galaxy.yml.
Consequently, all my playbooks that use inverse_inc.packetfence collection will not work.
Proposed Solution
When using --editable in place of using name of directory as symlink name, mazer should extract name value from galaxy.yml of collection to create a correct symlink name.
Alternatives
Having an extra argument to --editable option in order to create a symlink with a free name (like GNU ln command):
mazer install --namespace my_namespace --editable ~/src/collections/my_new_collection link_name
# in my case:
mazer install --namespace inverse_inc --editable ~/git/ansible-packetfence/ansible/ packetfence
Feature Request
Use Case
I use
--editable
option on an existing Ansible collection with following tree:like this:
This result with following symlink:
~/.ansible/collections/ansible_collections/inverse_inc/ansible/
but my collection has name
packetfence
mentioned inansible-packetfence/ansible/galaxy.yml
.Consequently, all my playbooks that use
inverse_inc.packetfence
collection will not work.Proposed Solution
When using
--editable
in place of using name of directory as symlink name,mazer
should extractname
value fromgalaxy.yml
of collection to create a correct symlink name.Alternatives
Having an extra argument to
--editable
option in order to create a symlink with a free name (like GNUln
command):