# dokploy_bitbucket_provider (Data Source)

Looks up a Bitbucket connection that is registered in Dokploy (Git > Bitbucket), so that the `bitbucket` source of an application or a compose does not hold a hardcoded id.

~> **`id` is the `bitbucketId`, not the `gitProviderId`.** An application references the Bitbucket-specific record.

~> The data source does not expose the app password or the API token.

## Example Usage

```terraform
# Look up a Bitbucket connection that already exists in Dokploy, by name.
data "dokploy_bitbucket_provider" "main" {
  name = "acme"
}

# Deploy an application from a Bitbucket repository through it.
resource "dokploy_application" "api" {
  name           = "api"
  environment_id = dokploy_project.app.production_environment_id

  bitbucket = {
    bitbucket_id    = data.dokploy_bitbucket_provider.main.id
    owner           = "acme"
    repository      = "api"
    repository_slug = "api"
    branch          = "main"
  }
}
```

<!-- schema generated by tfplugindocs -->
## Schema

### Optional

- `id` (String) The `bitbucketId`. Set it for a lookup by id, or leave it unset and set `name`.
- `name` (String) Provider name as shown in Dokploy. Set exactly one of `id` or `name`.

### Read-Only

- `created_at` (String) Creation timestamp from the server.
- `git_provider_id` (String) Id of the generic git-provider record.
- `is_configured` (Boolean) Whether Dokploy holds usable credentials.
- `is_deprecated` (Boolean) Whether the record uses the deprecated app-password shape.
- `shared_with_organization` (Boolean) Whether the provider is shared with the whole organization.
- `username` (String) Bitbucket username, or null for the API-token shape.