Enable YADE configurations to be deployed by Job Resources

Current Situation

• JOC Cockpit offers to manage YADE file transfer configurations.
• The configuration is available from an XML document that has to be downloaded and deployed to the target Agent that runs the YADE job.

Desired Behavior

• It is possible to assign a job resource a YADE configuration (XML document).
  • The GUI offers this assignment from the Configuration view for any Job Resource.
  • Assignment includes to optionally select a YADE configuration from the list of tabs as available with the Configuration->File Transfer sub-view as the value of a Job Resource Variable.
    • The same YADE configuration can be assigned a number of Job Resource Variables in the same or in different Job Resources.
      The Job Resource variable holds the contents of a YADE XML configuration, for example the Job Resource Agent_005 can be configured like this:

    • "variables": { "yade_config": '<xml/>' }
      

• When the YADE configuration is deployed - by use of the "Deploy" button in the Configuration->File Transfer sub-view - then any Job Resources are deployed that make use of the current YADE configuration.
• Run-time behavior with workflow execution:
  • A job that is assigned the Job Resource Variable does not directly receive the value of the variable but the path to a temporary file that holds this value, i.e. the contents of the YADE configuration. A job environment variable receives the the path to the temporary file like this:

    • "YADE_CONFIG": "jobResourceVariable( 'Agent_005', 'yade_config' ) )"
      

• • from the Agent_005 Job Resource the value of the yade_config variable is written to a file in the Agent's work directory with the name yade.xml.
    • The job script can use the $YADE_CONFIG environment variable that holds the absolute path to the YADE configuration from a file, e.g. $JS7_AGENT_DATA/work/yade.xml and use the environment variable for parameterization of the YADE CLI Client like this:

    • $JS7_YADE_BIN -settings $YADE_CONFIG -profile myTransfer
      

Delimitation

• This feature is made available starting from JS-1972 that includes to create a temporary file for each execution of a job referencing a Job Resource Variable that holds a YADE configuration.
• With JS-1976 the lifecycle of Job Resources is considered and the temporary file is created/updated/deleted only if the respective Job Resource is deployed or removed.

Maintainer Notes

• This issue is a duplicate for JOC-1224