Skip to main content

Temporal CLI worker command reference

View Markdown

This page provides a reference for the temporal CLI worker command. The flags applicable to each subcommand are presented in a table within the heading for the subcommand. Refer to Global Flags for flags that you can use with every subcommand.

deployment

Deployment commands perform operations on Worker Deployments:

temporal worker deployment [command] [options]

For example:

temporal worker deployment list

Lists the Deployments in the client's namespace.

Arguments can be Worker Deployment Versions associated with a Deployment, specified using the Deployment name and Build ID.

For example:

temporal worker deployment set-current-version \
--deployment-name YourDeploymentName --build-id YourBuildID

Sets the current Deployment Version for a given Deployment.

create

Create a new Worker Deployment:

temporal worker deployment create [options]

Worker Deployments are lazily created the first time a Worker polls the Temporal Server and specifies a VersionOverride. However, if you need to pre-define a compute configuration (for instance to set up a serverless Worker), you need to call temporal worker deployment create-version and pass in the name of the Worker Deployment. The temporal worker deployment create command allows you to pre-define a Worker Deployment so that calls to temporal worker deployment create-version will succeed.

If a Worker Deployment with the supplied name already exists, this command will return an error.

Note: This is an experimental feature and may change in the future.

Use the following options to change the behavior of this command. You can also use any of the global flags that apply to all subcommands.

FlagRequiredDescription
--name, -dYesstring Name for a Worker Deployment.

create-version

Create a new Worker Deployment Version:

temporal worker deployment create-version [options]

Configure a Worker Deployment Version's compute configuration as needed. For example, pass compute provider information for an AWS Lambda function that spawns a Worker in the Worker Deployment:

temporal worker deployment create-version \
--namespace YourNamespaceName \
--deployment-name YourDeploymentName \
--build-id YourBuildID \
--aws-lambda-function-arn LambdaFunctionARN \
--aws-lambda-assume-role-arn LambdaAssumeRoleARN \
--aws-lambda-assume-role-external-id LambdaAssumeRoleExternalID

Or pass compute provider information for an AWS Bedrock Agentcore Runtime that spawns a Worker in the Worker Deployment:

temporal worker deployment create-version \
--namespace YourNamespaceName \
--deployment-name YourDeploymentName \
--build-id YourBuildID \
--aws-agentcore-endpoint-arn AgentcoreRuntimeEndpointARN \
--aws-agentcore-assume-role-arn AgentcoreAssumeRoleARN \
--aws-agentcore-assume-role-external-id AgentcoreAssumeRoleExternalID

Or pass compute provider information for a GCP Cloud Run worker pool that spawns a Worker in the Worker Deployment:

temporal worker deployment create-version \
--namespace YourNamespaceName \
--deployment-name YourDeploymentName \
--build-id YourBuildID \
--gcp-cloud-run-project YourGCPProject \
--gcp-cloud-run-region us-central1 \
--gcp-cloud-run-worker-pool YourWorkerPool \
--gcp-cloud-run-service-account customer-sa@proj.iam.gserviceaccount.com \
--gcp-cloud-run-min-instances 1 \
--gcp-cloud-run-max-instances 3 \
--gcp-cloud-run-initial-instances 1 \
--gcp-cloud-run-utilization-target 0.75 \
--gcp-cloud-run-scale-down-stabilization-duration 5m

If a Worker Deployment Version with the supplied BuildID already exists, this command will return an error.

Returns an error if all compute configuration fields are empty.

Note: This is an experimental feature and may change in the future.

Use the following options to change the behavior of this command. You can also use any of the global flags that apply to all subcommands.

FlagRequiredDescription
--aws-agentcore-assume-role-arnNostring AWS IAM role ARN that the Temporal server will assume when invoking the Agentcore Runtime that spawns a new Worker in this Worker Deployment Version. Required when --aws-agentcore-endpoint-arn is specified, and must be omitted when --aws-agentcore-skip-role-and-external-id is passed.
--aws-agentcore-assume-role-external-idNostring Temporal server will enforce that the AWS IAM trust policy associated with the AWS IAM role specified in --aws-agentcore-assume-role-arn has an aws:ExternalId condition that matches the supplied value. Required when --aws-agentcore-endpoint-arn is specified, and must be omitted when --aws-agentcore-skip-role-and-external-id is passed.
--aws-agentcore-endpoint-arnNostring AWS Bedrock Agentcore Runtime endpoint ARN to invoke when there are no active pollers for task queue targets in the Worker Deployment. The endpoint ARN encodes the runtime, endpoint name, and region.
--aws-agentcore-skip-role-and-external-idNobool When --aws-agentcore-endpoint-arn is specified, --aws-agentcore-assume-role-arn and --aws-agentcore-assume-role-external-id are required unless this flag is passed, in which case both must be omitted.
--aws-lambda-assume-role-arnNostring AWS IAM role ARN that the Temporal server will assume when invoking the Lambda function that spawns a new Worker in this Worker Deployment Version. Required when --aws-lambda-function-arn is specified, and must be omitted when --aws-lambda-skip-role-and-external-id is passed.
--aws-lambda-assume-role-external-idNostring Temporal server will enforce that the AWS IAM trust policy associated with the AWS IAM role specified in --aws-lambda-assume-role-arn has an aws:ExternalId condition that matches the supplied value. Required when --aws-lambda-function-arn is specified, and must be omitted when --aws-lambda-skip-role-and-external-id is passed.
--aws-lambda-function-arnNostring Qualified (contains version suffix) or unqualified AWS Lambda function ARN to invoke when there are no active pollers for task queue targets in the Worker Deployment.
--aws-lambda-skip-role-and-external-idNobool When --aws-lambda-function-arn is specified, --aws-lambda-assume-role-arn and --aws-lambda-assume-role-external-id are required unless this flag is passed, in which case both must be omitted.
--build-idYesstring Build ID of the Worker Deployment Version.
--deployment-nameYesstring Name of the Worker Deployment.
--gcp-cloud-run-initial-instancesNoint Number of Cloud Run worker pool instances the scaler starts with. Optional, but --gcp-cloud-run-min-instances, --gcp-cloud-run-max-instances, --gcp-cloud-run-initial-instances, --gcp-cloud-run-utilization-target, and --gcp-cloud-run-scale-down-stabilization-duration must all be set together, and this value must be between the min and max (inclusive). Defaults to 0 when unset. Only valid with --gcp-cloud-run-worker-pool.
--gcp-cloud-run-max-instancesNoint Maximum number of Cloud Run worker pool instances the scaler may scale up to. Optional, but --gcp-cloud-run-min-instances, --gcp-cloud-run-max-instances, --gcp-cloud-run-initial-instances, --gcp-cloud-run-utilization-target, and --gcp-cloud-run-scale-down-stabilization-duration must all be set together. Defaults to 30 when unset. Only valid with --gcp-cloud-run-worker-pool.
--gcp-cloud-run-min-instancesNoint Minimum number of Cloud Run worker pool instances the scaler will maintain. Optional, but --gcp-cloud-run-min-instances, --gcp-cloud-run-max-instances, --gcp-cloud-run-initial-instances, --gcp-cloud-run-utilization-target, and --gcp-cloud-run-scale-down-stabilization-duration must all be set together. Defaults to 0 when unset. Only valid with --gcp-cloud-run-worker-pool.
--gcp-cloud-run-projectNostring GCP project ID hosting the Cloud Run worker pool. Required when --gcp-cloud-run-worker-pool is specified.
--gcp-cloud-run-regionNostring Region of the Cloud Run worker pool. Required when --gcp-cloud-run-worker-pool is specified.
--gcp-cloud-run-scale-down-stabilization-durationNoduration Duration the scaler waits after it last saw unmet task demand before it may scale the Cloud Run worker pool down. Raise this to keep the pool from scaling down before long-running or bursty activities finish. Optional, but --gcp-cloud-run-min-instances, --gcp-cloud-run-max-instances, --gcp-cloud-run-initial-instances, --gcp-cloud-run-utilization-target, and --gcp-cloud-run-scale-down-stabilization-duration must all be set together. A value of 0s disables the wait. Defaults to 90s when unset. Only valid with --gcp-cloud-run-worker-pool.
--gcp-cloud-run-service-accountNostring Customer GCP service account the Temporal server impersonates to manage the Cloud Run worker pool. Required when --gcp-cloud-run-worker-pool is specified.
--gcp-cloud-run-utilization-targetNofloat Target average worker utilization the scaler aims for, as a fraction in the range (0, 1]. Optional, but --gcp-cloud-run-min-instances, --gcp-cloud-run-max-instances, --gcp-cloud-run-initial-instances, --gcp-cloud-run-utilization-target, and --gcp-cloud-run-scale-down-stabilization-duration must all be set together. Lower values keep more spare capacity per worker. Defaults to 0.8 when unset. Only valid with --gcp-cloud-run-worker-pool.
--gcp-cloud-run-worker-poolNostring GCP Cloud Run worker pool name to scale when there are no active pollers for task queue targets in the Worker Deployment.

delete

Remove a Worker Deployment given its Deployment Name. A Deployment can only be deleted if it has no Version in it.

temporal worker deployment delete [options]

For example, setting the user identity that removed the deployment:

temporal worker deployment delete \
--name YourDeploymentName \
--identity YourIdentity

Use the following options to change the behavior of this command. You can also use any of the global flags that apply to all subcommands.

FlagRequiredDescription
--name, -dYesstring Name for a Worker Deployment.

delete-version

Remove a Worker Deployment Version given its fully-qualified identifier. This is rarely needed during normal operation since unused Versions are eventually garbage collected. The client can delete a Version only when all of the following conditions are met:

  • It is not the Current or Ramping Version for this Deployment.
  • It has no active pollers, i.e., none of the task queues in the Version have pollers.
  • It is not draining. This requirement can be ignored with the option --skip-drainage.
temporal worker deployment delete-version [options]

For example, skipping the drainage restriction:

temporal worker deployment delete-version \
--deployment-name YourDeploymentName --build-id YourBuildID \
--skip-drainage

Use the following options to change the behavior of this command. You can also use any of the global flags that apply to all subcommands.

FlagRequiredDescription
--build-idYesstring Build ID of the Worker Deployment Version.
--deployment-nameYesstring Name of the Worker Deployment.
--skip-drainageNobool Ignore the deletion requirement of not draining.

describe

Describe properties of a Worker Deployment, such as the versions associated with it, routing information of new or existing tasks executed by this deployment, or its creation time.

temporal worker deployment describe [options]

For example, to describe a deployment YourDeploymentName in the default namespace:

temporal worker deployment describe \
--name YourDeploymentName

Use the following options to change the behavior of this command. You can also use any of the global flags that apply to all subcommands.

FlagRequiredDescription
--name, -dYesstring Name for a Worker Deployment.

describe-version

Describe properties of a Worker Deployment Version, such as the task queues polled by workers in this Deployment Version, or drainage information required to safely decommission workers, or user-provided metadata, or its creation/modification time.

temporal worker deployment describe-version [options]

For example, to describe a deployment version in a deployment YourDeploymentName, with Build ID YourBuildID, and in the default namespace:

temporal worker deployment describe-version \
--deployment-name YourDeploymentName --build-id YourBuildID

Use the following options to change the behavior of this command. You can also use any of the global flags that apply to all subcommands.

FlagRequiredDescription
--build-idYesstring Build ID of the Worker Deployment Version.
--deployment-nameYesstring Name of the Worker Deployment.
--report-task-queue-statsNobool Report stats for task queues that are present in this version.

list

List existing Worker Deployments in the client's namespace.

temporal worker deployment list [options]

For example, listing Deployments in YourDeploymentNamespace:

temporal worker deployment list \
--namespace YourDeploymentNamespace

Use global flags to customize the connection to the Temporal Service for this command.

manager-identity

Manager Identity commands change the ManagerIdentity of a Worker Deployment:

temporal worker deployment manager-identity [command] [options]

When present, ManagerIdentity is the identity of the user that has the exclusive right to make changes to this Worker Deployment. Empty by default. When set, users whose identity does not match the ManagerIdentity will not be able to change the Worker Deployment.

This is especially useful in environments where multiple users (such as CLI users and automated controllers) may interact with the same Worker Deployment. ManagerIdentity allows different users to communicate with one another about who is expected to make changes to the Worker Deployment.

The current Manager Identity is returned with describe:

temporal worker deployment describe \
--deployment-name YourDeploymentName

set

Set the ManagerIdentity of a Worker Deployment given its Deployment Name.

When present, ManagerIdentity is the identity of the user that has the exclusive right to make changes to this Worker Deployment. Empty by default. When set, users whose identity does not match the ManagerIdentity will not be able to change the Worker Deployment.

This is especially useful in environments where multiple users (such as CLI users and automated controllers) may interact with the same Worker Deployment. ManagerIdentity allows different users to communicate with one another about who is expected to make changes to the Worker Deployment.

temporal worker deployment manager-identity set [options]

For example:

temporal worker deployment manager-identity set \
--deployment-name DeploymentName \
--self \
--identity YourUserIdentity # optional, populated by CLI if not provided

Sets the Manager Identity of the Deployment to the identity of the user making this request. If you don't specifically pass an identity field, the CLI will generate your identity for you.

For example:

temporal worker deployment manager-identity set \
--deployment-name DeploymentName \
--manager-identity NewManagerIdentity

Sets the Manager Identity of the Deployment to any string.

Use the following options to change the behavior of this command. You can also use any of the global flags that apply to all subcommands.

FlagRequiredDescription
--deployment-nameNostring Name for a Worker Deployment. Required.
--manager-identityNostring New Manager Identity. Required unless --self is specified.
--selfNobool Set Manager Identity to the identity of the user submitting this request. Required unless --manager-identity is specified.
--yes, -yNobool Don't prompt to confirm set Manager Identity.

unset

Unset the ManagerIdentity of a Worker Deployment given its Deployment Name.

When present, ManagerIdentity is the identity of the user that has the exclusive right to make changes to this Worker Deployment. Empty by default. When set, users whose identity does not match the ManagerIdentity will not be able to change the Worker Deployment.

This is especially useful in environments where multiple users (such as CLI users and automated controllers) may interact with the same Worker Deployment. ManagerIdentity allows different users to communicate with one another about who is expected to make changes to the Worker Deployment.

temporal worker deployment manager-identity unset [options]

For example:

temporal worker deployment manager-identity unset \
--deployment-name YourDeploymentName

Clears the Manager Identity field for a given Deployment.

Use the following options to change the behavior of this command. You can also use any of the global flags that apply to all subcommands.

FlagRequiredDescription
--deployment-nameNostring Name for a Worker Deployment. Required.
--yes, -yNobool Don't prompt to confirm unset Manager Identity.

set-current-version

Set the Current Version for a Deployment. When a Version is current, Workers of that Deployment Version will receive tasks from new Workflows, and from existing AutoUpgrade Workflows that are running on this Deployment.

If not all the expected Task Queues are being polled by Workers in the new Version the request will fail. To override this protection use --ignore-missing-task-queues. Note that this would ignore task queues in a deployment that are not yet discovered, leading to inconsistent task queue configuration.

temporal worker deployment set-current-version [options]

For example, to set the Current Version of a deployment YourDeploymentName, with a version with Build ID YourBuildID, and in the default namespace:

temporal worker deployment set-current-version \
--deployment-name YourDeploymentName --build-id YourBuildID

The target of set-current-version can also be unversioned workers:

temporal worker deployment set-current-version \
--deployment-name YourDeploymentName --unversioned

Use the following options to change the behavior of this command. You can also use any of the global flags that apply to all subcommands.

FlagRequiredDescription
--allow-no-pollersNobool Override protection and set version as current even if it has no pollers.
--build-idNostring Build ID of the Worker Deployment Version. Required unless --unversioned is specified.
--deployment-nameYesstring Name of the Worker Deployment.
--ignore-missing-task-queuesNobool Override protection to accidentally remove task queues.
--unversionedNobool Set unversioned workers as the target version. Cannot be used with --build-id.
--yes, -yNobool Don't prompt to confirm set Current Version.

set-ramping-version

Set the Ramping Version and Percentage for a Deployment.

The Ramping Version can be set using deployment name and build ID, or set to unversioned workers using the --unversioned flag.

The Ramping Percentage is a float with values in the range [0, 100]. A value of 100 does not make the Ramping Version Current, use set-current-version instead.

To remove a Ramping Version use the flag --delete.

If not all the expected Task Queues are being polled by Workers in the new Ramping Version the request will fail. To override this protection use --ignore-missing-task-queues. Note that this would ignore task queues in a deployment that are not yet discovered, leading to inconsistent task queue configuration.

temporal worker deployment set-ramping-version [options]

For example, to set the Ramping Version of a deployment YourDeploymentName, with a version with Build ID YourBuildID, with 10 percent of tasks redirected to this version, and using the default namespace:

temporal worker deployment set-ramping-version \
--deployment-name YourDeploymentName --build-id YourBuildID \
--percentage 10.0

And to remove that ramping:

temporal worker deployment set-ramping-version \
--deployment-name YourDeploymentName --build-id YourBuildID \
--delete

Use the following options to change the behavior of this command. You can also use any of the global flags that apply to all subcommands.

FlagRequiredDescription
--allow-no-pollersNobool Override protection and set version as ramping even if it has no pollers.
--build-idNostring Build ID of the Worker Deployment Version. Required unless --unversioned is specified.
--deleteNobool Delete the Ramping Version.
--deployment-nameYesstring Name of the Worker Deployment.
--ignore-missing-task-queuesNobool Override protection to accidentally remove task queues.
--percentageNofloat Percentage of tasks redirected to the Ramping Version. Valid range [0,100].
--unversionedNobool Set unversioned workers as the target version. Cannot be used with --build-id.
--yes, -yNobool Don't prompt to confirm set Ramping Version.

update-version-compute-config

Update compute configuration associated with a Worker Deployment Version.

For example, to update the AWS Lambda function ARN associated with an existing Worker Deployment Version:

temporal worker deployment update-version-compute-config \
--deployment-name YourDeploymentName --build-id YourBuildID \
--aws-lambda-function-arn UpdatedLambdaFunctionARN

To update the AWS IAM role ARN that is assumed by the serverless worker manager associated with an existing Worker Deployment Version:

temporal worker deployment update-version-compute-config \
--deployment-name YourDeploymentName --build-id YourBuildID \
--aws-lambda-assume-role-arn UpdatedRoleARN

To update the AWS Bedrock Agentcore Runtime endpoint associated with an existing Worker Deployment Version:

temporal worker deployment update-version-compute-config \
--deployment-name YourDeploymentName --build-id YourBuildID \
--aws-agentcore-endpoint-arn UpdatedAgentcoreRuntimeEndpointARN \
--aws-agentcore-assume-role-arn UpdatedRoleARN \
--aws-agentcore-assume-role-external-id UpdatedExternalID

To update the GCP Cloud Run worker pool associated with an existing Worker Deployment Version:

temporal worker deployment update-version-compute-config \
--deployment-name YourDeploymentName --build-id YourBuildID \
--gcp-cloud-run-project YourGCPProject \
--gcp-cloud-run-region us-central1 \
--gcp-cloud-run-worker-pool UpdatedWorkerPool \
--gcp-cloud-run-service-account customer-sa@proj.iam.gserviceaccount.com \
--gcp-cloud-run-min-instances 1 \
--gcp-cloud-run-max-instances 3 \
--gcp-cloud-run-initial-instances 1 \
--gcp-cloud-run-utilization-target 0.75 \
--gcp-cloud-run-scale-down-stabilization-duration 5m

To update only the scaling settings on an existing GCP Cloud Run Worker Deployment Version, supply the five scaler flags without the provider fields (all five must be set together):

temporal worker deployment update-version-compute-config \
--deployment-name YourDeploymentName --build-id YourBuildID \
--gcp-cloud-run-min-instances 1 \
--gcp-cloud-run-max-instances 3 \
--gcp-cloud-run-initial-instances 1 \
--gcp-cloud-run-utilization-target 0.75 \
--gcp-cloud-run-scale-down-stabilization-duration 5m

Provider fields are only required when changing the compute provider. Switching the provider resets the scaling settings for the new provider.

If --remove is specified, the compute configuration for the Worker Deployment Version will be removed:

temporal worker deployment update-version-compute-config \
--deployment-name YourDeploymentName --build-id YourBuildID \
--remove

If a Worker Deployment Version with the supplied BuildID does not exist, this command will return an error.

Note: This is an experimental feature and may change in the future.

Use the following options to change the behavior of this command. You can also use any of the global flags that apply to all subcommands.

FlagRequiredDescription
--aws-agentcore-assume-role-arnNostring AWS IAM role ARN that the Temporal server will assume when invoking the Agentcore Runtime that spawns a new Worker in this Worker Deployment Version. Required when --aws-agentcore-endpoint-arn is specified, and must be omitted when --aws-agentcore-skip-role-and-external-id is passed.
--aws-agentcore-assume-role-external-idNostring Temporal server will enforce that the AWS IAM trust policy associated with the AWS IAM role specified in --aws-agentcore-assume-role-arn has an aws:ExternalId condition that matches the supplied value. Required when --aws-agentcore-endpoint-arn is specified, and must be omitted when --aws-agentcore-skip-role-and-external-id is passed.
--aws-agentcore-endpoint-arnNostring AWS Bedrock Agentcore Runtime endpoint ARN to invoke when there are no active pollers for task queue targets in the Worker Deployment. The endpoint ARN encodes the runtime, endpoint name, and region.
--aws-agentcore-skip-role-and-external-idNobool When --aws-agentcore-endpoint-arn is specified, --aws-agentcore-assume-role-arn and --aws-agentcore-assume-role-external-id are required unless this flag is passed, in which case both must be omitted.
--aws-lambda-assume-role-arnNostring AWS IAM role ARN that the Temporal server will assume when invoking the Lambda function that spawns a new Worker in this Worker Deployment Version. Required when --aws-lambda-function-arn is specified, and must be omitted when --aws-lambda-skip-role-and-external-id is passed.
--aws-lambda-assume-role-external-idNostring Temporal server will enforce that the AWS IAM trust policy associated with the AWS IAM role specified in --aws-lambda-assume-role-arn has an aws:ExternalId condition that matches the supplied value. Required when --aws-lambda-function-arn is specified, and must be omitted when --aws-lambda-skip-role-and-external-id is passed.
--aws-lambda-function-arnNostring Qualified (contains version suffix) or unqualified AWS Lambda function ARN to invoke when there are no active pollers for task queue targets in the Worker Deployment.
--aws-lambda-skip-role-and-external-idNobool When --aws-lambda-function-arn is specified, --aws-lambda-assume-role-arn and --aws-lambda-assume-role-external-id are required unless this flag is passed, in which case both must be omitted.
--build-idYesstring Build ID of the Worker Deployment Version.
--deployment-nameYesstring Name of the Worker Deployment.
--gcp-cloud-run-initial-instancesNoint Number of Cloud Run worker pool instances the scaler starts with. Optional, but --gcp-cloud-run-min-instances, --gcp-cloud-run-max-instances, --gcp-cloud-run-initial-instances, --gcp-cloud-run-utilization-target, and --gcp-cloud-run-scale-down-stabilization-duration must all be set together, and this value must be between the min and max (inclusive). If omitted, the version's existing scaling settings are left unchanged. Only applies to a GCP Cloud Run worker pool.
--gcp-cloud-run-max-instancesNoint Maximum number of Cloud Run worker pool instances the scaler may scale up to. Optional, but --gcp-cloud-run-min-instances, --gcp-cloud-run-max-instances, --gcp-cloud-run-initial-instances, --gcp-cloud-run-utilization-target, and --gcp-cloud-run-scale-down-stabilization-duration must all be set together. If omitted, the version's existing scaling settings are left unchanged. Only applies to a GCP Cloud Run worker pool.
--gcp-cloud-run-min-instancesNoint Minimum number of Cloud Run worker pool instances the scaler will maintain. Optional, but --gcp-cloud-run-min-instances, --gcp-cloud-run-max-instances, --gcp-cloud-run-initial-instances, --gcp-cloud-run-utilization-target, and --gcp-cloud-run-scale-down-stabilization-duration must all be set together. If omitted, the version's existing scaling settings are left unchanged. Only applies to a GCP Cloud Run worker pool.
--gcp-cloud-run-projectNostring GCP project ID hosting the Cloud Run worker pool. Required when --gcp-cloud-run-worker-pool is specified.
--gcp-cloud-run-regionNostring Region of the Cloud Run worker pool. Required when --gcp-cloud-run-worker-pool is specified.
--gcp-cloud-run-scale-down-stabilization-durationNoduration Duration the scaler waits after it last saw unmet task demand before it may scale the Cloud Run worker pool down. Raise this to keep the pool from scaling down before long-running or bursty activities finish. Optional, but --gcp-cloud-run-min-instances, --gcp-cloud-run-max-instances, --gcp-cloud-run-initial-instances, --gcp-cloud-run-utilization-target, and --gcp-cloud-run-scale-down-stabilization-duration must all be set together. A value of 0s disables the wait. If omitted, the version's existing scaling settings are left unchanged. Only applies to a GCP Cloud Run worker pool.
--gcp-cloud-run-service-accountNostring Customer GCP service account the Temporal server impersonates to manage the Cloud Run worker pool. Required when --gcp-cloud-run-worker-pool is specified.
--gcp-cloud-run-utilization-targetNofloat Target average worker utilization the scaler aims for, as a fraction in the range (0, 1]. Optional, but --gcp-cloud-run-min-instances, --gcp-cloud-run-max-instances, --gcp-cloud-run-initial-instances, --gcp-cloud-run-utilization-target, and --gcp-cloud-run-scale-down-stabilization-duration must all be set together. Lower values keep more spare capacity per worker. If omitted, the version's existing scaling settings are left unchanged. Only applies to a GCP Cloud Run worker pool.
--gcp-cloud-run-worker-poolNostring GCP Cloud Run worker pool name to scale when there are no active pollers for task queue targets in the Worker Deployment.
--removeNobool Removes any compute configuration associated with this Worker Deployment Version.

update-version-metadata

Update metadata associated with a Worker Deployment Version.

For example:

temporal worker deployment update-version-metadata \
--deployment-name YourDeploymentName --build-id YourBuildID \
--metadata bar=1 \
--metadata foo=true

The current metadata is also returned with describe-version:

temporal worker deployment describe-version \
--deployment-name YourDeploymentName --build-id YourBuildID \

Use the following options to change the behavior of this command. You can also use any of the global flags that apply to all subcommands.

FlagRequiredDescription
--build-idYesstring Build ID of the Worker Deployment Version.
--deployment-nameYesstring Name of the Worker Deployment.
--metadataNostring[] Set deployment metadata using KEY="VALUE" pairs. Keys must be identifiers, and values must be JSON values. For example: YourKey={"your": "value"} Can be passed multiple times.
--remove-entriesNostring[] Keys of entries to be deleted from metadata. Can be passed multiple times.

describe

Look up information of a specific worker.

temporal worker describe --namespace YourNamespace --worker-instance-key YourKey

Use the following options to change the behavior of this command. You can also use any of the global flags that apply to all subcommands.

FlagRequiredDescription
--worker-instance-keyYesstring Worker instance key to describe.

list

Get a list of workers to the specified namespace.

temporal worker list --namespace YourNamespace --query 'TaskQueue="YourTaskQueue"'

Use the following options to change the behavior of this command. You can also use any of the global flags that apply to all subcommands.

FlagRequiredDescription
--limitNoint Maximum number of workers to display.
--query, -qNostring Content for an SQL-like QUERY List Filter.

Global Flags

The following options can be used with any command.

FlagRequiredDescriptionDefault
--addressNostring Temporal Service gRPC endpoint.localhost:7233
--api-keyNostring API key for request.
--client-authorityNostring Temporal gRPC client :authority pseudoheader.
--client-connect-timeoutNoduration Client connection timeout.
--codec-authNostring Authorization header for Codec Server requests.
--codec-endpointNostring Remote Codec Server endpoint.
--codec-headerNostring[] HTTP headers for codec server (KEY=VALUE, repeatable).
--colorNostring-enum Output coloring. Accepted values: always, never, auto.auto
--command-timeoutNoduration Command execution timeout.
--config-fileNostring TOML config file path.
--disable-config-envNobool Disable loading config from environment variables.
--disable-config-fileNobool Disable loading config from file.
--envNostring Active environment name (ENV).default
--env-fileNostring Path to environment settings file.
--grpc-metaNostring[] HTTP headers for requests (KEY=VALUE, repeatable).
--identityNostring Identity of the client submitting requests.
--log-formatNostring-enum Log format. Accepted values: text, json.text
--log-levelNostring-enum Log level. Default is "never" for most commands and "warn" for "server start-dev". Accepted values: debug, info, warn, error, never.never
--namespace, -nNostring Temporal Service Namespace.default
--no-json-shorthand-payloadsNobool Raw payload output, even if the JSON option was used.
--output, -oNostring-enum Non-logging data output format. Accepted values: text, json, jsonl, none.text
--profileNostring Profile to use for config file.
--time-formatNostring-enum Time format. Accepted values: relative, iso, raw.relative
--tlsNobool Enable base TLS encryption. Auto-enabled when api-key or TLS options are set.
--tls-ca-dataNostring Inline server CA certificate data.
--tls-ca-pathNostring Path to server CA certificate.
--tls-cert-dataNostring Inline x509 certificate data.
--tls-cert-pathNostring Path to x509 certificate.
--tls-disable-host-verificationNobool Disable TLS host-name verification.
--tls-key-dataNostring Inline x509 private key data.
--tls-key-pathNostring Path to x509 private key.
--tls-server-nameNostring Override target TLS server name.