John Schoewe
John Schoewe
It sounds like you want to fork the Jira pack and then add your new actions to that forked repo. And then instead of running `st2 pack install jira` you...
St2 version 3.1.0 action/test_workflow.yaml: --- name: test_workflow pack: test description: Test workflow runner_type: orquesta entry_point: workflows/test_workflow.yaml enabled: true parameters: test_param1: type: string description: "This does not fail if test_param1 does...
We are running stackstorm version 3.8 and just ran into this issue as well. We updated our sensors to use `self._sensor_service.get_value` instead of `st2_client.keys.get_by_name` as @amanda11 suggested and we are...
Seeing as this references a deprecated mistral workflow and publishing and passing arrays works fine in orquesta, I'd say this bug can be closed
Still seeing this issue in st2 3.8.0, on Python 3.8.13
This issue seems to be resolved in st2 3.8.0. I'm no longer seeing a traceback with inquiry errors ``` [root@stackstorm ~]# st2 inquiry get abc123 Inquiry "abc123" is not found....
I've never used this CI tool before but I'm kind of confused because it's giving me syntax errors in files that I didn't touch. Should I fix those as well?