Can you associate a mistral workflow execution with an environment via the CLI?

asked 2017-04-19 13:04:13 -0500

mattybrennan
41 ●1 ●3 ●8

I can create an environment, and I can create a workflow execution. But I don't see any way via the CLI to associate a workflow or a workflow execution with an environment

usage: mistral environment-create [-h] [-f {json,shell,table,value,yaml}]
                              [-c COLUMN] [--max-width <integer>]
                              [--print-empty] [--noindent]
                              [--prefix PREFIX]
                              file

-

usage: mistral workflow-create [-h] [-f {csv,json,table,value,yaml}]
                           [-c COLUMN] [--max-width <integer>]
                           [--print-empty] [--noindent]
                           [--quote {all,minimal,none,nonnumeric}]
                           [--public]
                           definition

-

usage: mistral execution-create [-h] [-f {json,shell,table,value,yaml}]
                            [-c COLUMN] [--max-width <integer>]
                            [--print-empty] [--noindent] [--prefix PREFIX]
                            [-d DESCRIPTION]
                            workflow_identifier [workflow_input] [params]

edit retag flag offensive close merge delete

add a comment

3

answered 2017-04-20 07:52:20 -0500

zaneb
1724 ●4 ●22 ●28 https://www.zerobanana...

When you define an environment inline, you pass it with the "env" key as part of the [params] argument (which is in JSON format IIUC). I'm not sure how that applies to predefined environments created through the API though.

edit flag offensive delete link

Comments

Thanks! This solves my problem.

mattybrennan ( 2017-04-25 10:58:32 -0500 )edit

It was confirmed in IRC that the following works, where my_env is the name of the predefined environment mistral execution-create $WORKFLOW '' '{"env": "my_env"}'

mattybrennan ( 2017-06-06 12:59:50 -0500 )edit

add a comment

2

answered 2017-04-25 10:28:32 -0500

d0ugal
71 ●1 ●8

updated 2017-04-26 03:06:31 -0500

I don't think there is a way to link a pre-existing environment. You could, however, have a task in the workflow that fetches the environment. This workflow takes the name of a environment, it then fetches it and outputs the contents of the environment.

wf:
  input:
    - env_name
  tasks:
    get_env:
      action: mistral.environments_get name=<% $.env_name %>
      publish:
        env: task(get_env).result.variables
      on-complete: do_something
    do_something:
      action: std.echo output=<% $.env %>

edit flag offensive delete link

Comments

Thanks. I guess I don't understand when the pre-existing environments are ever used then.

mattybrennan ( 2017-04-25 10:58:13 -0500 )edit

This worked me too, provided that mistral.environments_get is working. I bet d0ugal's example worked when he posted it. I ran into an issue where it didn't work for me with mistral client 3.1.0 until I applied a fix destined for 3.1.1. Details in bug: https://bugs.launchpad.net/mistral/+bug/1696128 (https://bugs.launchpad.net/mistral/+b...)