Skip to content

BES configuration is a workflow parameter instead of hard-coded

Wout De Nolf requested to merge bes_port_not_in_config into main

We should try avoiding hard-coded configuration imo.

This MR starts with the BES port to be used when a workflow task needs to connect to BES. It is now added by BES to inData when executing the workflow.

What convention in terms of camel-case or underscores should we keep when adding new variable names, workflow parameters, functions etc? I called it besConfiguration both as a python variable and a workflow parameter. Is that correct?

Merge request reports