The Bitbucket integration has a special discovery processor for discovering catalog entities located in Bitbucket. The processor will crawl your Bitbucket account and register entities matching the configured path. This can be useful as an alternative to static locations or manually adding things to the catalog.
Note: The Bitbucket Discovery Processor currently only supports a self-hosted Bitbucket Server, and not the hosted Bitbucket Cloud product.
To use the discovery processor, you'll need a Bitbucket integration
set up with a
BITBUCKET_TOKEN and a
Then you can add a location target to the catalog configuration:
catalog: locations: - type: bitbucket-discovery target: https://bitbucket.mycompany.com/projects/my-project/repos/service-*/catalog-info.yaml
bitbucket-discovery type, as this is not a regular
The target is composed of four parts:
- The base instance URL,
https://bitbucket.mycompany.comin this case
- The project key to scan, which accepts * wildcard tokens. This can simply be
*to scan repositories from all projects. This example only scans for repositories in the
- The repository blob to scan, which accepts * wildcard tokens. This can simply
*to scan all repositories in the project. This example only looks for repositories prefixed with
- The path within each repository to find the catalog YAML file. This will
/catalog-info.yamlor a similar variation for catalog files stored in the root directory of each repository.