Skip to content

docs: update Bitbucket Cloud receiver guidance #1346

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
stefanprodan merged 1 commit into from
Jul 22, 2026
Merged

docs: update Bitbucket Cloud receiver guidance #1346

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 27 additions & 5 deletions docs/spec/v1/receivers.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -468,11 +468,12 @@ the `X-Event-Key` header to the list of [Events](#events). For a list of
available event keys, refer to the [Bitbucket Server
documentation](https://confluence.atlassian.com/bitbucketserver/event-payload-938025882.html#Eventpayload-Repositoryevents).

**Note:** Bitbucket Cloud does not support signing webhook requests
([BCLOUD-14683](https://jira.atlassian.com/browse/BCLOUD-14683),
[BCLOUD-12195](https://jira.atlassian.com/browse/BCLOUD-12195)). If your
repositories are on Bitbucket Cloud, you will need to use a [Generic
Receiver](#generic) instead.
Bitbucket Cloud also supports signed webhooks using the same `X-Hub-Signature`
header validation. Configure a webhook secret in your repository settings and
use the `bitbucket` receiver type with the appropriate Cloud event keys (for
example `repo:push`). See the [Bitbucket Cloud webhook
documentation](https://support.atlassian.com/bitbucket-cloud/docs/manage-webhooks/)
for setup details.

##### Bitbucket Server example

Expand Down Expand Up @@ -500,6 +501,27 @@ incoming events from Bitbucket Server, instructing the controller to only
respond to [`repo:refs_changed` (Push)](https://confluence.atlassian.com/bitbucketserver/event-payload-938025882.html#Eventpayload-Push)
events.

##### Bitbucket Cloud example

```yaml
---
apiVersion: notification.toolkit.fluxcd.io/v1
kind: Receiver
metadata:
name: bitbucket-cloud-receiver
namespace: default
spec:
type: bitbucket
events:
- "repo:push"
secretRef:
name: webhook-token
resources:
- apiVersion: source.toolkit.fluxcd.io/v1
kind: GitRepository
name: webapp
```

#### Harbor

When a Receiver's `.spec.type` is set to `harbor`, the controller will respond
Expand Down