Skip to main content
PATCH
Update a blueprint's contents and/or position

Permissions

Requires a service user with the ManageRepoBlueprints permission at the organization level. Creating or updating org-tier blueprints requires the ManageOrgSnapshots permission.

Behavior

Updates a blueprint’s contents and/or position. Does not auto-trigger a build.

Authorizations

Authorization
string
header
required

Service User credential (prefix: cog_)

Path Parameters

blueprint_id
string
required
org_id
string
required

Organization ID (prefix: org-)

Example:

"org-abc123def456"

Body

application/json

Partial update for an org- or repo-tier blueprint.

Any subset of fields may be provided. Fields not set are left alone. Providing position on an org-tier blueprint returns 400 — only repo-tier blueprints have a position. Does NOT trigger a build.

contents
string | null

If set, replaces the blueprint's YAML body with a new version.

position
integer | null

If set, updates the execution position of this repo-tier blueprint. Positions are not required to be unique; ties are broken arbitrarily by the server when sorting for execution.

Response

Successful Response

Public Blueprint resource shape.

Note: the type enum may grow in the future; clients MUST gracefully handle unknown values. YAML contents are fetched separately via GET /blueprints/{id}/contents.

blueprint_id
string
required
created_at
integer
required
repo_name
string | null
required
type
enum<string>
required
Available options:
enterprise,
org,
repo
updated_at
integer
required