Bitbucket Pipelines: sync secrets

Export secrets into one Bitbucket repository's pipeline variables.

Connection

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

Direction	What it does
`export`	We write names and values from your environment into the store.

Bitbucket returns no value once it holds one, so we 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.

Paste a credential from the vendor. We seal it and never show it again.

Field	Label	Kind	Required	What it is
`token`	Access token	secret; we mask it here and seal it	yes	A Repository or Workspace Access Token carrying pipeline:variable. The similar-looking pipeline:write does not grant variable writes.

You set these when you connect. Every mapping on the connection shares them.

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.

You answer these 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.

We probe for these when we verify 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.