Enterprise allows you to configure an ActionConfig dynamically, e.g. in a workflow execution, an existing groovy script can update and set the configuration to be used by the following ActionConfig using a json-metadata-instance
.
JEF supports <_action-node-name_>-json-metadata-instance
dynamic updates if the context variable is set in the workflow before job execution, e.g. setting the following workflow context variable will change the configuration of the “Smoke 1” Action Config:
{
<span class="hljs-string">"Smoke 1-json-metadata-instance"</span> : <span class="hljs-string">"{\"expected-success\": false,\"milliseconds-to-wait\":
100,\"count\": \"1\", \"resume-supported\":false,\"update-interval\":1}"</span>
}
If the configured json-metadata-instance
is incorrect and no ActionConfiguration can be instanced, the following occurs: