sincecutoff.com
/v1/json /v1/md llms.txt
← all changes

temporal Nexus operation CLI adds standalone operation support

Introduced 2026-09-11 · score 0.94

HOW TO USE IT

When connecting to an OSS server v1.32.0, start a standalone Nexus operation with `temporal nexus operation start`, supplying its endpoint, service, operation, operation ID, and JSON input. The release note identifies this command group as experimental.

temporal operator nexus endpoint create --name <endpoint> --target-namespace <namespace> --target-task-queue <task-queue>
temporal nexus operation start --endpoint <endpoint> --service <service> --operation <operation> --operation-id <operation-id> --input '"<value>"'

WHY THIS HELPS

Start or inspect standalone Nexus operations from the CLI when using an OSS server v1.32.0.

REQUIREMENTS AND LIMITATIONS

  • Version: v1.9.0
  • --name (required): Endpoint name.
  • --target-namespace (required): Target namespace for the endpoint.
  • --target-task-queue (required): Target task queue for the endpoint.
  • --endpoint (required): Endpoint to invoke.
  • --service (required): Nexus service to invoke.
  • --operation (required): Operation to start.
  • --operation-id (required): Operation ID.
  • --input: JSON input payload; the source example passes a JSON string.
  • Prerequisite: Requires OSS Server v1.32.0.
  • Prerequisite: The release note labels the `temporal nexus operation` command group Experimental.
  • Requires OSS server version v1.32.0.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card