common-workflow-language / cwl-v1.3

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Collecting new features for CWL v1.3

mr-c opened this issue · comments

See https://github.com/common-workflow-language/common-workflow-language/milestone/10 for other ideas ; which ones do we want to implement for CWL v1.3?

From discussion at CWL conference hackathon

add "secret" to input parameter

"secret" field can be

  • null (default, not secret)
  • false (same as null)
  • true (value is secret)
  • a non-empty string -- (1) if a value for the input parameter is not provided by the caller, and (2) the platform provides a secret vault, this is the lookup key that will be used to request a secret from the platform. The format and scope of this lookup key are implementation specific and not defined by this spec.

If "secret" is provided, the "type" of the input parameter can only be "string" or "string[]", plus "null" if the secret is optional. If "secret" is a string and the platform supports looking up credentials, the input parameter is implicitly optional (but it is a fatal error if the platform does not support secret storage or the lookup fails).