gcp-run-update-config
match (effective permission)
{
"action": "run.services.update",
"resource_type": "google.cloud.run.Service"
}
emit
| source type | Identity |
|---|---|
| target type | * |
| source | <principal> |
| target | <Cloud Run service/job/worker-pool in scope> |
| permissions | run.services.update run.jobs.update run.workerpools.update |
Narrative
{principal.name} can modify the configuration of {resource.name} (run.services.update / run.jobs.update): env, secrets, command, ingress, or identity.
Raw rule rules/derived/gcp/cloudrun.yaml
id: gcp-run-update-config
emits: CanModifyConfiguration
match_effective_permission:
action: run.services.update
resource_type: google.cloud.run.Service
alt_permission: run.jobs.update
emit:
source_type: Identity
target_type: '*'
source: <principal>
target: <Cloud Run service/job/worker-pool in scope>
permissions:
- run.services.update
- run.jobs.update
- run.workerpools.update
escalation: Change env vars, secret mounts, command/args, ingress, or the runtime SA on a new revision.
note: Changing the runtime SA to a different SA additionally requires iam.serviceAccounts.actAs on that
SA (see gcp-run-set-runtime-sa).
narrative: '{principal.name} can modify the configuration of {resource.name} (run.services.update /
run.jobs.update): env, secrets, command, ingress, or identity.'