Bitbucket Pipelines

Export secrets into one Bitbucket repository's pipeline variables.

The connection

What	This provider
Vendor	Bitbucket
Key	`bitbucket-variables`
Availability	`available`. You can connect it today.
Credential penv holds	`bitbucket-token`
Values read back	no
Activation	`immediate`

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

Bitbucket 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`	Access token	secret, masked here and sealed	yes	A Repository or Workspace Access Token carrying pipeline:variable. The similar-looking pipeline:write does not grant variable writes.

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

Field	Label	Kind	Required	Advanced	What it is
`workspace`	Workspace	text	yes	no	The first path segment of your repository's URL. One connection covers one workspace.

Answered once per environment you map.

Field	Label	Kind	Required	Advanced	What it is
`repository`	Repository	text	yes	no	Names starting with BITBUCKET_ are accepted, and override Bitbucket's own build variables.

penv probes for these when it verifies the connection.

Permission	Directions	Blocking	Without it
`pipeline`	every direction	yes	Preview cannot list what is already there, so a prune cannot be planned.
`pipeline:variable`	`export`	yes	Export cannot write anything.