Access remote sources

Every plugin command accepts the same runtime connection options. Place them after the plugin name and before or after other plugin options:

transpiler-mate <plugin> [RUNTIME_OPTIONS] [PLUGIN_OPTIONS] SOURCE

Authenticate to HTTP and HTTPS

Set a bearer token:

export OAUTH2_BEARER="your-token"
transpiler-mate <plugin> [PLUGIN_OPTIONS] https://example.org/tool.cwl

Or pass it directly:

transpiler-mate <plugin> \
  --oauth2-bearer "your-token" \
  [PLUGIN_OPTIONS] \
  https://example.org/tool.cwl

Without a token, the runtime uses a standard HTTP adapter. With a token, it mounts a bearer-authentication adapter for both HTTP and HTTPS.

Authenticate to OCI

Prefer environment variables for credentials:

export OCI_HOSTNAME="registry.example.org"
export OCI_USERNAME="your-user"
export OCI_PASSWORD="your-password"
transpiler-mate <plugin> [PLUGIN_OPTIONS] oci://namespace/tool:tag

The equivalent command options are --oci-hostname, --oci-username, and --oci-password.

Select a process in a remote document

Append a fragment to the source:

transpiler-mate <plugin> [PLUGIN_OPTIONS] \
  oci://namespace/workflow:tag#main

See Select a process for the selection behavior.

Warning

Command-line secrets may be recorded in shell history and visible to other local processes. Prefer the supported environment variables or your platform's secret injection facility.