Bitbucket Provider

Generate Provider

The Bitbucket provider must be installed as a Local Package by following the instructions for Any Terraform Provider:

pulumi package add terraform-provider drfaust92/bitbucket

Overview

The Bitbucket provider allows you to manage resources including repositories, webhooks, and default reviewers.

Use the navigation to the left to read about the available resources.

Configuration Reference

The following configuration inputs are supported in the provider configuration:

• username - (Optional) Username to use for authentication via Basic Auth. When using an API token, this must be your Atlassian account email address. You can also set this via the BITBUCKET_USERNAME environment variable. If configured, requires password to be configured as well.

• password - (Optional) Password to use for authentication via Basic Auth. It is recommended to use an API Token created at Atlassian Account Settings as your password, with your Atlassian account email as the username. Note: Bitbucket App Passwords are deprecated and will stop working on June 9, 2026. You can also set this via the BITBUCKET_PASSWORD environment variable. If configured, requires username to be configured as well.

• oauthClientId - (Optional) OAuth client ID to use for authentication via Client Credentials Grant. You can also set this via the BITBUCKET_OAUTH_CLIENT_ID environment variable. If configured, requires oauthClientSecret to be configured as well.

• oauthClientSecret - (Optional) OAuth client secret to use for authentication via Client Credentials Grant. You can also set this via the BITBUCKET_OAUTH_CLIENT_SECRET environment variable. If configured, requires oauthClientId to be configured as well.

• oauthToken - (Optional) An OAuth access token, or a workspace, project or repository access token, sent as a bearer token. You can also set this via the BITBUCKET_OAUTH_TOKEN or BITBUCKET_ACCESS_TOKEN environment variable. Access tokens are not tied to a user, so bitbucket.getCurrentUser, the group resources and functions, and deploy keys don’t work with them.

Permission Scopes

To interact with the Bitbucket API, an API Token or OAuth Client Credentials are required.

API tokens and OAuth client credentials are limited in scope, each API requires certain scope to interact with, each resource doc will specify what scopes are required to use that resource:

• OAuth 2.0 scopes
• API token permissions