Hi Support-Team:
Recently，I encountered a problem and I want to report it to you ,When I call the sub-process in the
process, the default value of the enumeration type displays the first value in the enumeration type on
the front-end page, instead of the default value.So I think this is a bug. When I run the sub-process
separately and adjust other parameters, the default value of the enumeration type parameter will be
displayed correctly on the front end.Below I will list the process and cases in detail.
The workflow is as follow:
Action/orquasta.yaml
name: orquesta-basic
pack: redis
description: Run a local linux command
runner_type: orquesta
entry_point: workflows/orquasta.yaml
enabled: true
parameters:
cmd:
required: true
type: string
timeout:
type: integer
default: 60
Workflows/orquasta.yaml
version: 1.0
description: A basic workflow that runs an arbitrary linux command.
input:
- cmd
- timeout
tasks:
task1:
action: redis.output_para
input:
main_idc: <% ctx(cmd) %>
Action/output_para.yaml
name: “output_para”
description: “[workflow] .”
runner_type: “python-script”
enabled: true
entry_point: “output_para.py”
pack: redis
parameters:
main_idc:
type: “string”
description: “main idc code.”
required: true
enum:
- SHAJQ
- SHAOY
- SHARB
- CFTRB
- CFTJQ
- SIN-AWS
- FRA-AWS
- SFO-AWS
- YMQ-AWS
- SHA-ALI
- “None”
position: 0
default: “CFTJQ”
policy:
type: “string”
description: “not enum type,default 2”
required: true
default: ‘2’
position: 1
cluster_type:
type: “string”
description: “enum type,default 3”
required: true
enum:
- ‘0’
- ‘2’
- ‘3’
- ‘4’
- ‘5’
default: ‘3’
position: 2
Action/output_para.yaml
-- coding: utf-8 --
from st2common.runners.base_action import Action
class output(Action):
def run(self,main_idc,policy,cluster_type):
print(main_idc,policy,cluster_type)
return True
The cases is as follow:
1》Main process call sub process case：
The output result is not equal to the input result displayed on the front end
2》Run sub-processes independently and adjust main_idc parameter,the cluster_type parameter will be adjusted.Otherwise, the front-end display is still wrong.
1.outer parameters have not been adjusted.
- Other parameters have been adjusted
So far my conclusion is：
1,Parameter trigger update is carried out after any parameter adjustment
2,When the main process is called the sub-process, even if there are other parameter adjustments, it
will not trigger the default value parameter adjustment displayed on the front-end
That’s all, please reply after receiving
Thank you