You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 30, 2020. It is now read-only.
Similar to pip install -e. The -e option will enable Ansible to find and execute content found in a local project directory structure.
As a developer I want to create a new collection, so I run mazer init foo, to create a new Ansible Collection named foo in the current working directory. This new project is not in the Ansible content path, so Ansible cannot see any of the content I add to the collection.
To make the content visible to Ansible, I will run mazer install -e foo, and Mazer will add the appropriate symlinks, and thus make any new content added to the project accessible to Ansible.
The command should support:
. for the current working directory
A path to a project
A -g or --global option to add the project to the global content path
The text was updated successfully, but these errors were encountered:
Similar to
pip install -e
. The-e
option will enable Ansible to find and execute content found in a local project directory structure.As a developer I want to create a new collection, so I run
mazer init foo
, to create a new Ansible Collection named foo in the current working directory. This new project is not in the Ansible content path, so Ansible cannot see any of the content I add to the collection.To make the content visible to Ansible, I will run
mazer install -e foo
, and Mazer will add the appropriate symlinks, and thus make any new content added to the project accessible to Ansible.The command should support:
.
for the current working directory-g
or--global
option to add the project to the global content pathThe text was updated successfully, but these errors were encountered: