Update a trigger
PATCH/v1/projects/:project_id/triggers/:trigger_id
Updates an existing trigger's configuration. The type is immutable. Changing target_type or target_id re-checks that the caller may start the resulting target, because a firing acts under the trigger's policy_ids rather than the updater's grant. A caller who could not start the new target is answered 403 and the trigger keeps the target it had. A {{secret:...}} reference in a written tool_context, or in the stored one when the target changes, also needs secrets:UseSecret on that secret, else 403. An update leaving an event trigger's policy_ids unable to read a platform namespace its events subscribe to is refused with 400 EVENTS_UNREADABLE.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 413
- 429
- 500
- 502
- 4XX
Trigger updated
Bad request
Unauthorized
Forbidden
Trigger not found
REQUEST_REJECTED — the request body is over the size the body parser accepts
QUOTA_EXCEEDED — a requests quota on the calling API key or its project is spent for the window; Retry-After says when it reopens
Response Headers
Seconds until the quota window admits a request again
Unexpected server error — INTERNAL_ERROR, with the raw message never forwarded
The deployment's admission service is asked about this write and did not answer — ADMISSION_UNAVAILABLE; the write did not happen
The deployment's admission service refused this write — answered under the service's own 4xx status, with its code (matching ^[A-Za-z_][A-Za-z0-9_]{0,63}$, not necessarily an ERROR_CODES key), message and meta; the write did not happen. A status this operation also declares on its own is documented there