Skip to main content

Bitbucket Cloud Locations

The Bitbucket Cloud integration supports loading catalog entities from bitbucket.org. Entities can be added to static catalog configuration, or registered with the catalog-import plugin.

Configuration​

API token usage example (recommended):

integrations:
  bitbucketCloud:
    - username: user@domain.com # username -> user email
      token: my-token

Legacy:

integrations:
  bitbucketCloud:
    - username: username
      appPassword: my-password
Note

A public Bitbucket Cloud provider is added automatically at startup for convenience, so you only need to list it if you want to supply credentials.

Note

The credential required for this type is either an Api token or an App Password. An Atlassian Account API key will not work.

Directly under the bitbucketCloud key is a list of provider configurations, where you can list the Bitbucket Cloud providers you want to fetch data from. In the case of Bitbucket Cloud, you will have up to one entry.

This one entry will have the following elements:

  • username: The Bitbucket Cloud username to use in API requests. If neither a username nor token are supplied, anonymous access will be used.
  • token: The token used to authenticate requests.
  • appPassword: The app password for the Bitbucket Cloud user.