Arvados

Publishing:

1. workflow record gets new fields: git_repository_uuid, git_commit, workflow_path, properties (for metadata)
2. "publish" API call takes git_repository_uuid, git_commit, workflow_path; scans workflow, checks validity, and creates/updates workflow record with extracted metadata (such as name, description, inputs)
3. "Run" button in workbench (or API call?) sets up container with mount point: git_repository_uuid, git_commit; runs arvados-cwl-runner with CWL file located at git mount/workflow_path

Alternative to explicit "publish" API is to use a git hook on commit which scans repository for CWL files matching a certain pattern and registers/updates them automatically. This closes the loop and make publishing a workflow as simple as a git commit. More discussion/proof of concept at https://dev.arvados.org/issues/10344#note-4