garadar
garadar
Dear old favorite collaborative customer
I have the same error, if you are using a different home than /home/stanley: ``` getent passwd stanley stanley:x:900:900::/opt/xxxx/xxx/home/stanley:/bin/bash ``` but `core.remote ` using `remote-shell-cmd `by default take a bad...
OMHO, stackstorm should read the $HOME of stanley instead /home/stanley by default
indeed it could; I will try Thx
It's 'working' However, the one line command does not work if you create the stanley user with a custom home before the install.
I search in /opt/stackstorm/st2 tree, I find where the trigger are created but did not find how the instance called/generated. Do you have an idea? I will try to fix...
Hello, Any news on this issue ? :)
Hi @arm4b @cognifloyd Do you have any information on this problem? It would be really interesting to have this option to fully automate certain workflows.
Thank you, Here my workflow:  ^ ```YAML version: 1.0 description: "Engage the deletion process" input: - username # Be careful, to the filename vars: - tmp_mail_path: '/opt/stackstorm/packs/blablabla/actions/workflows/template' - mail_file:...
> Are you doing this via re-run of previous runs? Or brand new flow runs? Each time is a new execution of the workflows