Add GCP min/max scaling options for worker deployment version

[zainawaisn]

Related issues

What changed?

Adds three new (optional) flags gcp-cloud-run-min-instances, gcp-cloud-run-max-instances, and gcp-cloud-run-initial-instances to create-version and update-version-compute-config.

temporal worker deployment create-version \
    --deployment-name YourDeployment \
    --build-id YourBuildID \
    --gcp-cloud-run-project YourProject \
    --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 0 \
    --gcp-cloud-run-max-instances 10 \
    --gcp-cloud-run-initial-instances 5

temporal worker deployment update-version-compute-config \
    --deployment-name YourDeployment \
    --build-id YourBuildID \
    --gcp-cloud-run-project YourProject \
    --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 0 \
    --gcp-cloud-run-max-instances 10 \
    --gcp-cloud-run-initial-instances 5

Changes

• commands.yaml / commands.gen.go: two new flags
  (--gcp-cloud-run-min-instances, --gcp-cloud-run-max-instances) on
  create-version and update-version-compute-config, plus help text (optional,
  must be paired, defaults 0/30) and usage examples.

• commands.worker.deployment.go: a new gcpCloudRunScalerDetails helper turns
  the flags into the scaling settings sent to the server, and rejects bad input
  early (GCP-only, all three required together, and min <= initial <= max).
  Both commands use it, and describe-version now shows the settings back in
  its JSON and summary output.

• tests: unit tests cover the helper's accept/reject cases and the
  describe-version display; command-level error cases were added to
  TestCreateWorkerDeploymentVersion_Errors. The end-to-end GCP test stays
  skipped (needs real GCP resources).

Checklist

Stability

• Breaking changes are marked with 💥 in the PR title and release notes
• Changes to JSON output (-o json / -o jsonl) are treated as breaking changes

Design

• This feature does not depend on Cloud-only APIs or behavior (it works against an OSS server)
• New commands follow temporal <noun> <verb> structure (e.g. temporal workflow start)
• New flags are named after the API concept, not the implementation mechanism (good: --search-attribute, bad: --index-field)
• New flags don't duplicate an existing flag that serves the same purpose
• New flags do not have short aliases without strong justification
• Experimental features are marked with (Experimental) in commands.yaml

Help text (see style guide at the top of commands.yaml)

• All flags shown in help text and examples are implemented and functional
• Summaries use sentence case and have no trailing period
• Long descriptions end with a period and include at least one example invocation
• Examples use long flags (--namespace, not -n), one flag per line
• Placeholder values use YourXxx form (YourWorkflowId, YourNamespace)

Behavior

• Results go to stdout; errors and warnings go to stderr
• Error messages are lowercase with no trailing punctuation

Tests

• Added functional test(s) (SharedServerSuite)
• Added unit test(s) (func TestXxx) where applicable

Manual tests

Creation:

./temporal --profile "ns-cloud-run-test" worker deployment create-version \
    --deployment-name "zain-cloud-run-deployment" \
    --build-id "1.0" \
    --gcp-cloud-run-project "compute-team-sandbox" \
    --gcp-cloud-run-region "us-west1" \
    --gcp-cloud-run-worker-pool "omes-worker-pool" \
    --gcp-cloud-run-service-account "wci-invocation-sa@compute-team-sandbox.iam.gserviceaccount.com" \
    --gcp-cloud-run-min-instances 0 \
    --gcp-cloud-run-max-instances 10 \
    --gcp-cloud-run-initial-instances 5
Successfully created worker deployment version

./temporal --profile "ns-cloud-run-test" worker deployment describe-version \
    --deployment-name "zain-cloud-run-deployment" \
    --build-id "1.0" \
    --output json
...
        "scaler": {
          "type": "rate-based",
          "minInstances": 0,
          "maxInstances": 10,
          "initialInstances": 5
        }
...

Update existing:

./temporal --profile "ns-cloud-run-test" worker deployment update-version-compute-config \
    --deployment-name "zain-cloud-run-deployment" \
    --build-id "1.0" \
    --gcp-cloud-run-project "compute-team-sandbox" \
    --gcp-cloud-run-region "us-west1" \
    --gcp-cloud-run-worker-pool "omes-worker-pool" \
    --gcp-cloud-run-service-account "wci-invocation-sa@compute-team-sandbox.iam.gserviceaccount.com" \
    --gcp-cloud-run-min-instances 5 \
    --gcp-cloud-run-max-instances 15 \
    --gcp-cloud-run-initial-instances 10
Successfully updated worker deployment version compute config

./temporal --profile "ns-cloud-run-test" worker deployment describe-version \
    --deployment-name "zain-cloud-run-deployment" \
    --build-id "1.0" \
    --output json
{
...
        "scaler": {
          "type": "rate-based",
          "minInstances": 5,
          "maxInstances": 15,
          "initialInstances": 10
        }
...

Error checks:

./temporal --profile "ns-cloud-run-test" worker deployment create-version \
    --deployment-name "cli-cloud-run-deployment" \
    --build-id "1.0" \
    --gcp-cloud-run-project "compute-team-sandbox" \
    --gcp-cloud-run-region "us-west1" \
    --gcp-cloud-run-worker-pool "omes-worker-pool" \
    --gcp-cloud-run-service-account "wci-invocation-sa@compute-team-sandbox.iam.gserviceaccount.com" \
    --gcp-cloud-run-min-instances 11 \
    --gcp-cloud-run-max-instances 10 \
    --gcp-cloud-run-initial-instances 5
Error: --gcp-cloud-run-min-instances cannot exceed --gcp-cloud-run-max-instances

./temporal --profile "ns-cloud-run-test" worker deployment create-version \
    --deployment-name "cli-cloud-run-deployment" \
    --build-id "1.0" \
    --gcp-cloud-run-project "compute-team-sandbox" \
    --gcp-cloud-run-region "us-west1" \
    --gcp-cloud-run-worker-pool "omes-worker-pool" \
    --gcp-cloud-run-service-account "wci-invocation-sa@compute-team-sandbox.iam.gserviceaccount.com" \
    --gcp-cloud-run-min-instances 5 \
    --gcp-cloud-run-max-instances 10 \
    --gcp-cloud-run-initial-instances 0
Error: --gcp-cloud-run-initial-instances must be between --gcp-cloud-run-min-instances and --gcp-cloud-run-max-instances

./temporal --profile "ns-cloud-run-test" worker deployment create-version \
    --deployment-name "cli-cloud-run-deployment" \
    --build-id "1.0" \
    --gcp-cloud-run-project "compute-team-sandbox" \
    --gcp-cloud-run-region "us-west1" \
    --gcp-cloud-run-worker-pool "omes-worker-pool" \
    --gcp-cloud-run-service-account "wci-invocation-sa@compute-team-sandbox.iam.gserviceaccount.com" \
    --gcp-cloud-run-min-instances 0 \
    --gcp-cloud-run-initial-instances 5
Error: --gcp-cloud-run-min-instances, --gcp-cloud-run-max-instances, and --gcp-cloud-run-initial-instances must be set together

./temporal --profile "ns-cloud-run-test" worker deployment create-version \
    --deployment-name my-deploy --build-id v1 \
    --aws-lambda-function-arn arn:aws:lambda:us-east-1:123:function:F:1 \
    --aws-lambda-assume-role-arn arn:aws:iam::123:role/R \
    --aws-lambda-assume-role-external-id x \
    --gcp-cloud-run-min-instances 0 \
    --gcp-cloud-run-max-instances 10 \
    --gcp-cloud-run-initial-instances 5
Error: --gcp-cloud-run-min-instances, --gcp-cloud-run-max-instances, and --gcp-cloud-run-initial-instances are only valid with --gcp-cloud-run-worker-pool

[CLAassistant]

All committers have signed the CLA.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[ericbriffa]

Are more coming? or did we agree on just these?

Previous discussion was https://temporaltechnologies.slack.com/archives/C05L7RUSK6E/p1784055551940739

I updated https://temporalio.atlassian.net/browse/COM-222 with that data once I found it.

[zainawaisn]

synced with george on this, i believe min/max is fine for now.

scratch that, initial_count must not be lower than min_count, we should expose that as well. currently initial_count is a default 0 and cannot be changed via cli.