Buildkite cluster secrets

Export secrets into a Buildkite cluster.

The connection

What	This provider
Vendor	Buildkite
Key	`buildkite-cluster-secrets`
Availability	`available`. You can connect it today.
Credential penv holds	`buildkite-token`
Values read back	no
Activation	`immediate`

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

Buildkite returns no value once it holds one, so penv can write here and cannot read back.

immediate. The running app sees a new value at once.

Direction	Policies you can pick
`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
`token`	API access token	secret, masked here and sealed	yes	An API access token with read_secret_details and write_secrets.

Answered once per environment you map.

Field	Label	Kind	Required	Advanced	What it is
`organizationSlug`	Organization	text	yes	no	The slug in your Buildkite URL.
`clusterId`	Cluster	text	yes	no	Secrets belong to one cluster. Its ID is in the cluster's URL.

penv probes for these when it verifies the connection.

Permission	Directions	Blocking	Without it
`read_secret_details`	every direction	yes	Preview cannot list the cluster's secrets.
`write_secrets`	`export`	yes	Export cannot write anything.