summaryrefslogtreecommitdiffstats
path: root/ansible_collections/infinidat/infinibox/README-DEV.md
diff options
context:
space:
mode:
Diffstat (limited to 'ansible_collections/infinidat/infinibox/README-DEV.md')
-rw-r--r--ansible_collections/infinidat/infinibox/README-DEV.md21
1 files changed, 21 insertions, 0 deletions
diff --git a/ansible_collections/infinidat/infinibox/README-DEV.md b/ansible_collections/infinidat/infinibox/README-DEV.md
new file mode 100644
index 000000000..23bb71db0
--- /dev/null
+++ b/ansible_collections/infinidat/infinibox/README-DEV.md
@@ -0,0 +1,21 @@
+# Infinidat's Ansible Collection Development
+
+Installing Ansible using pip from within a venv caused an error much later in the dev process. When installing a collection built in this environment this error occurred:
+```
+$ make galaxy-collection-install-locally
+================ [ Begin galaxy-collection-install-locally ] ================
+ansible-galaxy collection install --force infinidat-infinibox-1.4.0.tar.gz --collections-path $HOME/.ansible/collections
+Starting galaxy collection install process
+Process install dependency map
+Starting collection install process
+Installing 'infinidat.infinibox:1.4.0' to '/home/stack/.ansible/collections/ansible_collections/infinidat/infinibox'
+ERROR! Unexpected Exception, this is probably a bug: "linkname 'venv/lib/python3.8/site-packages/ansible_test/_data/injector/python.py' not found"
+```
+
+Therefor using a venv is not recommended. Instead use the following that will install ansible commands into `~/.local/bin`.
+```
+$ python3 -m pip install --user ansible
+$ export PATH=/home/stack/.local/bin:$PATH
+```
+
+