when i exec "st2 packs install a" ,but b was installed!!!!why?
SUMMARY
when i exec "st2 packs install a" ,but b was installed!
STACKSTORM VERSION
Paste the output of st2 --version:
OS, environment, install method
Post what OS you are running this on, along with any other relevant information/
- e.g. Docker, Vagrant, Kubernetes, etc. Describe how you installed ST2
- e.g. one-line install, custom install, etc -->
Steps to reproduce the problem
1.st2 pack install file:///opt/stackstorm/packs/sre_publish_handle
when i exec "st2 packs install a" ,but b was installed!
2.sre_publish_handle/packs.yml
ref="sre_publish_handle"
3.sre_alarm_handle/packs.yml
ref="sre_alarm_handle"
4.st2 pack list
the sre_publish_handle was in pack list
5. ls -al virtualenvs
i can`t find the documen that name is "sre_publish_handle" whit in virtualenvs
Expected Results
i think the pack of sre_pubish_handle should be installed finally. but i don`t know why......
the version is: st2 3.8.0, on Python 3.8.10
I think if your application package is written correctly and you put it in /opt/stackstorm/packs/, it will be installed when you execute st2 reload.
I think if your application package is written correctly and you put it in /opt/stackstorm/packs/, it will be installed when you execute st2 reload.
yes, when i execute st2 reload, the pack that in /opt/stackstorm/packs will be install,but the virtual environment doesn`t be created.so i need use "st2 packs install file://xxxx" to install packs
yes, when i execute st2 reload, the pack that in /opt/stackstorm/packs will be install,but the virtual environment doesn`t be created.so i need use "st2 packs install file://xxxx" to install packs
you can also execute packs.setup_virtualenv. I do this in a orquesta workflow with newly created packs. I create template yaml files > packs.load > packs.setup_virtualenv > python script to add to RBAC > sudo st2-apply-rbac-definitions