MELT scripts build logic dependent on the script invocation path. The invocation path on Cromwell is a deployment-specific configuration, and currently, the default settings on GCP and Azure differ, which breaks MELT execution. We have two possible tracks to address this: (1) update the scripts to match the currently configured invocation path on Azure and GCP, or (2) update the scripts to be independent of the invocation path. This PR implements the latter approach as it seems more portable and invariant to deployment-specific configurations of Cromwell.
Specifically, this PR implements the following:
[x] Remove invocation path-dependent logic from MELT script and WDL;
[x] Update MELT docker and update dockers*.json accordingly.
The changes were successfully tested on GCP and Azure:
VJalili
commented
5 months ago
MELT scripts build logic dependent on the script invocation path. The invocation path on Cromwell is a deployment-specific configuration, and currently, the default settings on GCP and Azure differ, which breaks MELT execution. We have two possible tracks to address this: (1) update the scripts to match the currently configured invocation path on Azure and GCP, or (2) update the scripts to be independent of the invocation path. This PR implements the latter approach as it seems more portable and invariant to deployment-specific configurations of Cromwell.
Specifically, this PR implements the following:
dockers*.jsonaccordingly.The changes were successfully tested on GCP and Azure:
77c2629e-a0a7-4701-a3c0-97f7cd7a0aac;e168090f-c684-474e-84fd-6b51d0c3ddd0.