Skip to content
This repository has been archived by the owner on May 27, 2021. It is now read-only.

Mistral workflow fully qualified action name error #357

Open
jinpingh opened this issue Apr 25, 2019 · 2 comments
Open

Mistral workflow fully qualified action name error #357

jinpingh opened this issue Apr 25, 2019 · 2 comments

Comments

@jinpingh
Copy link

jinpingh commented Apr 25, 2019

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 message Name of the workflow must be the same as the fully qualified action name "examples.test_mistral_wf"

/opt/stackstorm/packs/examples/actions/test_mistral_wf.meta.yaml
pack: examples
enabled: true
runner_type: mistral-v2
name: test_mistral_wf
entry_point: workflows/test_mistral_wf.yaml
/opt/stackstorm/packs/examples/actions/workflows/test_mistral_wf.yaml
version: '2.0'
main:
  tasks:
    # [246, 304]
    task1:
      action: core.echo
      input:
        message: hello

mistral_wf

@Kami
Copy link
Member

Kami commented Apr 25, 2019

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.

@m4dcoder
Copy link
Contributor

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants