Make MELT scripts independent of the execution path. #665
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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*.json
accordingly.The changes were successfully tested on GCP and Azure:
77c2629e-a0a7-4701-a3c0-97f7cd7a0aac
;e168090f-c684-474e-84fd-6b51d0c3ddd0
.