GCP Cloud Run CLI

The Paradime SDK provides CLI commands to interact with Google Cloud Run, allowing you to trigger Cloud Run Jobs by name and list the jobs available in a project and region.

🔑 Authentication RequiredYou will need a GCP service account JSON key file with permissions to trigger and list Cloud Run Jobs in your project. Provide it via the --service-account-key-file flag or the GCP_SERVICE_ACCOUNT_KEY_FILE environment variable.

Trigger Cloud Run Jobs

Trigger one or more Cloud Run Jobs by name, optionally waiting for their execution to complete.

CLI Command

paradime run gcp-cloud-run-trigger

Options

Flag	Type	Description
`--service-account-key-file`	Required, TEXT	Path to your GCP service account JSON key file. Can be set via `GCP_SERVICE_ACCOUNT_KEY_FILE` environment variable.
`--project`	Required, TEXT	Your GCP project ID. Can be set via `GCP_PROJECT_ID` environment variable.
`--location`	Required, TEXT	GCP region (e.g. ‘us-central1’). Can be set via `GCP_LOCATION` environment variable.
`--job-names`	Required, TEXT	Comma-separated Cloud Run Job name(s) to trigger.
`--wait` / `--no-wait`	Optional, Flag	Wait for the job execution to complete before returning. Default: `--wait`. Can be set via `GCP_CLOUD_RUN_TRIGGER_WAIT` environment variable.
`--timeout`	Optional, INTEGER	Maximum time to wait for completion (in minutes). Only used with `--wait`. Default: 1440. Can be set via `GCP_CLOUD_RUN_TRIGGER_TIMEOUT` environment variable.
`--help`	Optional, Flag	Show the help message and exit.

Recommended SetupFor security and convenience, set your GCP credentials as environment variables:

GCP_SERVICE_ACCOUNT_KEY_FILE="/path/to/service-account-key.json"
GCP_PROJECT_ID="your_project_id"
GCP_LOCATION="us-central1"

Usage Examples

# Trigger a single job (using environment variables)
paradime run gcp-cloud-run-trigger \
  --job-names "my-job"

# Trigger multiple jobs
paradime run gcp-cloud-run-trigger \
  --job-names "etl-job,cleanup-job"

# With explicit credentials and no wait
paradime run gcp-cloud-run-trigger \
  --service-account-key-file "/path/to/key.json" \
  --project "your_project_id" \
  --location "us-central1" \
  --job-names "my-job" \
  --no-wait

List Cloud Run Jobs

List all Cloud Run Jobs in the specified project and region.

CLI Command

paradime run gcp-cloud-run-list

Options

Flag	Type	Description
`--service-account-key-file`	Required, TEXT	Path to your GCP service account JSON key file. Can be set via `GCP_SERVICE_ACCOUNT_KEY_FILE` environment variable.
`--project`	Required, TEXT	Your GCP project ID. Can be set via `GCP_PROJECT_ID` environment variable.
`--location`	Required, TEXT	GCP region (e.g. ‘us-central1’). Can be set via `GCP_LOCATION` environment variable.
`--help`	Optional, Flag	Show the help message and exit.

Usage Examples

# List all jobs (using environment variables)
paradime run gcp-cloud-run-list

# With explicit credentials
paradime run gcp-cloud-run-list \
  --service-account-key-file "/path/to/key.json" \
  --project "your_project_id" \
  --location "us-central1"

Environment Variable Reference

Environment Variable	Description
`GCP_SERVICE_ACCOUNT_KEY_FILE`	Path to your GCP service account JSON key file
`GCP_PROJECT_ID`	Your GCP project ID
`GCP_LOCATION`	GCP region (e.g. ‘us-central1’)
`GCP_CLOUD_RUN_TRIGGER_WAIT`	Wait for the job execution to complete before returning
`GCP_CLOUD_RUN_TRIGGER_TIMEOUT`	Maximum time to wait for completion (in minutes)

API Keys & Access

GraphQL API

Python SDK

Paradime CLI

Webhooks

Virtual Environments

GCP Cloud Run CLI

Trigger Cloud Run Jobs

CLI Command

Options

Usage Examples

List Cloud Run Jobs

CLI Command

Options

Usage Examples

Environment Variable Reference

​Trigger Cloud Run Jobs

​CLI Command

​Options

​Usage Examples

​List Cloud Run Jobs

​CLI Command

​Options

​Usage Examples

​Environment Variable Reference

Trigger Cloud Run Jobs

CLI Command

Options

Usage Examples

List Cloud Run Jobs

CLI Command

Options

Usage Examples

Environment Variable Reference