Open jinpingh opened 5 years ago
Thanks for finding and reporting this.
I confirmed - issue is related to _
in the action (and as such workflow name, if one is not explicitly specified in the workflow definition). -
works fine.
This is not a blocker for v3.0.0, but in the future we should fix it to at least throw a more user-friendly exception in such scenario.
In the WF definition, main
should be <pack>.<name>
from action meta. This is limitation of mistral WF definition and due to way that it stores individual workflows and workbooks in DB. Orquesta does not have this limitation.
st2 --version st2 3.0.0, on Python 2.7.6
Created and saved a new mistral workflow with name
test_mistral_wf
. Execution failed on error messageName of the workflow must be the same as the fully qualified action name "examples.test_mistral_wf"