Google Cloud Run jobs

Environment variables on a Cloud Run job's first container, read back in plaintext and applied to the next execution.

The connection

What	This provider
Vendor	Google Cloud
Key	`gcp-cloud-run-job-env`
Availability	`available`. You can connect it today.
Credential penv holds	`gcp-service-account`
Values read back	yes
Activation	`on-next-deploy`

Direction	What it does
`import`	Reads names and values out of the store into penv.
`export`	Writes names and values from penv into the store.

on-next-deploy. A new value waits there and arrives with your next deploy.

Direction	Policies you can pick
`import`	`skip_existing`, `new_version`, `fail`
`export`	`create_only`, `overwrite`, `overwrite_and_prune`

How syncs work says what each one does.

You paste a credential you already hold. penv seals it and never shows it again.

Field	Label	Kind	Required	What it is
`serviceAccountKey`	Service account key	secret, masked here and sealed	yes	The JSON key file for a service account that can update this job.

Fixed when you connect, and shared by every mapping on it.

Field	Label	Kind	Required	Advanced	What it is
`projectId`	Project	text	yes	no	The project holding the job. One connection covers one project.
`region`	Region	text	yes	no	The region this connection reaches. One connection covers one region.

Answered once per environment you map.

Field	Label	Kind	Required	Advanced	What it is
`jobName`	Job	text	yes	no	The job whose variables this environment maps onto.

penv probes for these when it verifies the connection.

Permission	Directions	Blocking	Without it
`run.jobs.get`	every direction	yes	Preview cannot read the job's variables.
`run.jobs.list`	every direction	no	We cannot confirm the key reaches this project and region before a sync runs.
`run.jobs.update`	`export`	yes	Export cannot write anything.
`run.operations.get`	`export`	no	We cannot confirm the update finished applying.