modernized developer docs based on new workflows with tox-ansible and… #33
Conversation
robled
force-pushed
the
devdocs
branch
2 times, most recently
from
b9ccd4a to
dcce9c2
Compare
| [ansible_collection_system](https://github.com/oasis-roles/ansible_collection_system) | ||
| collection. Git submodules are used to bring in shared repo dependencies. | ||
|
|
||
| `git clone --recurse-submodules [email protected]:oasis-roles/ansible_collection_system.git` |
There was a problem hiding this comment.
It might be worth mentioning that, in order to operate properly on these, you need to git clone this within the proper folder structure:
mkdir -p ansible_collections/oasis_roles
cd ansible_collections/oasis_roles
git clone --recurse-submodules [email protected]:oasis-roles/ansible_collection_system.git systemAnd then to set the value of ANSIBLE_COLLECTIONS_PATH or the collections_path in your ansible.cfg folder to the parent of the ansible_collections folder.
There was a problem hiding this comment.
Doing this would mean running the molecule_openstack_ci role from the master branch as well as the tests, correct? In the past I've just been running that stuff from the default location of ~/.ansible/collections using the latest released version. Do we want to run from master when we're just developing a new role?
Running molcule_openstack_ci and the tests from master seems like a separate area of concern (CI development?) compared to new role development.
I could be off base here since I'm still trying to understand all of the changes to our development process.
… Molecule