Bitbucket Connector

The Bitbucket connector ingests data from Bitbucket Cloud into the Context Catalog. It runs through the ibdm binary in one of two modes:

Sync — pull-based: queries the Bitbucket REST API and exits.
Run — push-based: exposes a webhook endpoint that receives Bitbucket events.

Commands

ibdm sync bitbucket --mapping-file <path to mapping file or folder>
ibdm run  bitbucket --mapping-file <path to mapping file or folder>

Variable	Required	Default	Description
`BITBUCKET_ACCESS_TOKEN`	One auth mode	—	Bitbucket access token for Bearer auth (workspace, project, or repository scope).
`BITBUCKET_API_USERNAME`	One auth mode	—	Username for HTTP Basic Authentication.
`BITBUCKET_API_TOKEN`	One auth mode	—	App password / access token for Basic Auth.
`BITBUCKET_URL`	No	`https://api.bitbucket.org`	Base URL of the Bitbucket API.
`BITBUCKET_HTTP_TIMEOUT`	No	`30s`	Timeout for HTTP requests (Go duration).
`BITBUCKET_WORKSPACE`	No	(empty)	Restrict sync to a single workspace slug. When empty, `ibdm` enumerates all accessible workspaces.
`BITBUCKET_WEBHOOK_SECRET`	Run	(empty)	HMAC secret for webhook signature validation.
`BITBUCKET_WEBHOOK_PATH`	No	`/bitbucket/webhook`	HTTP path for inbound webhook events.

Bitbucket supports two mutually exclusive authentication modes. Setting both is a configuration error.

Bearer Token — set BITBUCKET_ACCESS_TOKEN. Sent as Authorization: Bearer <token>.
Basic Auth — set both BITBUCKET_API_USERNAME and BITBUCKET_API_TOKEN. Sent as HTTP Basic Authentication.

Type	Sync	Webhook
`repository`	✅	✅
`pipeline`	✅	—

Subscribed webhook events: