paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 27 Packages Projects Releases Wiki Activity

feat(catalog): trigger entity updates based on Bitbucket Cloud's repo:updated events

Browse Source 
Signed-off-by: Patrick Jungermann <Patrick.Jungermann@gmail.com>
This commit is contained in:
Patrick Jungermann
2025-04-08 22:31:06 +02:00
parent 57ad208c85
commit 3bce578997
4 changed files with 347 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/integrations/bitbucketCloud/discovery.md
+17
View File
@@ -12,6 +12,23 @@ The provider will search your Bitbucket Cloud account and register catalog files
as Location entity and via following processing steps add all contained catalog entities.
This can be useful as an alternative to static locations or manually adding things to the catalog.
## Event-based Discovery
Supported events for event-based updates:
- [`repo:push`](https://support.atlassian.com/bitbucket-cloud/docs/event-payloads/#Push)
received as `bitbucket.repo:push`
- [`repo:updated`](https://support.atlassian.com/bitbucket-cloud/docs/event-payloads/#Updated)
received as `bitbucket.repo:updated`
- Changes are triggered if the repository slug/name changed, causing a new URL for it.
To receive events, you need to add webhook subscriptions at Bitbucket Cloud.
Enable the triggers (event types) you want to receive.
For the entity provider, only the event types above are supported ("Repository Push" and/or "Repository Updated")
and additional event types will be ignored (e.g., for other use cases/integrations you might have).
For more information on how to set up the event-based discovery, see the installation instructions below.
## Installation
You will have to add the entity provider in the catalog initialization code of your