weave
module · Code & DevOps

Bitbucket

Bitbucket — workspaces, repos, branch restrictions

Namespace: weave bitbucket Env: BITBUCKET_USER
3
Commands
1
State kinds
Code & DevOps
Category
1
API docs

Setup

Configure credentials via environment variables. We recommend sourcing them through 1Password or your secrets manager rather than committing them to the shell rc.

Official API reference

weave commands for this module are checked against the vendor's published API.

Variable Description Status
BITBUCKET_USERRequired for authentication.required
BITBUCKET_TOKENRequired for authentication.required

Sanity-check the wiring:

weave secrets check
weave bitbucket --help
weave doctor   # reports BITBUCKET_USER status

Capabilities

What this module can do, by entity and verb. means a working CLI surface; · means not (yet) wired.

Entity findlistshowdosnapshotdiffapply
repo······
resources····
user······
workspace······

Commands

Every registered CLI command, grouped by verb. Each example uses placeholder arguments — substitute real values for your environment.

find (1)

find user

read

Find a Bitbucket user.

weave bitbucket find user <username>

list (2)

list repos

read

List repositories in a workspace.

weave bitbucket list repos <arg>

list workspaces

read

List workspaces.

weave bitbucket list workspaces <arg>
snapshot / diff / apply are generated automatically from the State Kinds declared on this module — see the State kinds section below for per-kind details. Workflow: snapshot → edit YAML → diffapply --yes (or confirm interactively; apply --dry-run previews the same diff).

State kinds

Resources this module can snapshot and diff; apply where the kind supports live writes (see Round-trip per kind). Always run diff before apply; use --yes in automation after review. Files live under .weave-state/bitbucket/.

This module is on the thinner integration path — use snapshot / diff for audit; confirm apply per kind below before relying on writes.

resources

snapshot diff apply

bitbucket resources — field-level apply via REST.

Scope
Round-trip
Full round-trip — snapshot, diff, apply.

State file skeleton

module: bitbucket
kind: resources
items:
  - # <fields specific to this kind — see snapshot output>

Workflows

End-to-end recipes from operators who already run this module in production. Copy, adapt, and put under change-control.

Resources audit

Snapshot and diff resources.

weave bitbucket snapshot resources
$EDITOR .weave-state/bitbucket/resources.yaml
weave bitbucket diff resources
weave bitbucket apply resources

Terraform parity

For each Terraform resource in the canonical provider, here's the equivalent live-API verb in weave. Use this as a migration cheat-sheet, not a 1:1 contract — weave deliberately stays in the live-state lane, not the desired-state lane.

Terraform resource weave equivalent
bitbucket_resourcesweave bitbucket snapshot/diff/apply resources
Snapshot/diff for audit; confirm apply on the module page.

Troubleshooting & source

Missing credentials

Run weave doctor — it reports which env vars (including BITBUCKET_USER) are set and which are blank.

Unexpected behaviour from a state apply

Re-run weave bitbucket diff <kind> to confirm the controller's current state, then re-snapshot before the next apply. The driver always re-snapshots before diffing.