ignore the environment variable for dynamic value (with $), which should be generated during the Celery task generation
only generate environment variable for Task (commandLineTool), the envVarRequirement defined in the workflow should be inherited, but there is some potential issue.
if a workflow cwl file also contains envVarReq (example analytics_automated/tests/example_cwl_file/fake_workflow.cwl), it should transfer this value to all its tasks, and hence the task could then inherit the env variable.
Lack of multiple file update feature
If we upload the cwl task file and cwl workflow as different files (from lines 45-57 in cwl_workflow_handler), the task file will not be updated (lack code to hold this function)!
analytics_automated/tests/example_cwl_file/fake_workflow.cwl), it should transfer this value to all its tasks, and hence the task could then inherit the env variable.Lack of multiple file update feature
If we upload the cwl task file and cwl workflow as different files (from lines 45-57 in
cwl_workflow_handler), the task file will not be updated (lack code to hold this function)!