Consider the lifecycle of temporary files provided for values of variables from orders, workflows and job resources

Current Situation

• With JS-1972 temporary files are created if users access
  • the value of variable by use of the fileContent() function, for example when assigning an environment variable MY_VAR like this:

    • "MY_VAR": "fileContent( $someVar, ${js7Unique} +++ '-yade.xml',  )"
      

    • a temporary file is created in the Agent's work sub-directory with a unique prefix and the fixed part -yade.xml.
  • the value of a Job Resources that holds a YADE configuration like this:

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

• Temporary files are created for each execution of a job.

Desired Behavior

• Temporary files are created and updated only if the respective workflow or job resource is deployed.
  • Between deployments the temporary file remains in place.
  • If the Agent is restarted then the temporary file will be re-created.
• Temporary files are removed if the workflow and/or Job Resource is removed from the Agent.

Maintainer Notes

• The feature brings more complexity and little benefit.
• There's no harm in having temporary files created per job execution. The optimization to save 1ms when writing a temporary file is not in proportion to the complexity of introducing life cycle management.