Oracle Cloud Infrastructure Documentation

Creating a Bitbucket Cloud Configuration Source Provider

Create a configuration source provider in Resource Manager from Bitbucket Cloud.

Before You Begin

To connect Oracle Cloud Infrastructure Resource Manager to a Bitbucket Cloud repository, you must first create a Bitbucket Cloud API token with read scope (limited permissions).

See API token permissions.

When creating the API token:

  • Use your Atlassian account email for Bitbucket API authentication.
  • Store the API token in an OCI Vault secret.
  • Recommended scope: read:repository:bitbucket.
  • After completing all the prerequisites, follow these steps in the Console to create a configuration source provider from Bitbucket Cloud.
    1. On the Configuration source providers list page, select Create configuration source provider. If you need help finding the list page or the configuration source provider, see Listing Configuration Source Providers.
    2. In the Create configuration source provider panel, enter a name and optional description for the configuration source provider. Avoid entering confidential information.
    3. Select the compartment that you want to store the configuration source provider in.
    4. (Optional) To use a private endpoint, follow these steps:
      1. Select Private endpoint.
      2. Select or create a private endpoint. To select a private endpoint or certificate in a different compartment, select Change Compartment.
      3. Select an SSL certificate.
      For more information about private endpoints for private servers, see Private Git Server.
    5. For Type, select Bitbucket Cloud.
    6. Enter the following values:
      • Server URL: The Bitbucket Cloud service endpoint. Example: https://bitbucket.org/
      • Email: Atlassian account email used with the Bitbucket Cloud API token.
      • Vault: Vault where the secret is stored.
      • Secret: Secret for authorization.
        Note

        The secret contains the Bitbucket Cloud API token, not an app password.
    7. (Optional) Add one or more tags to the configuration source provider: Select Show advanced options to show tagging options.
      If you have permissions to create a resource, then you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. For more information about tagging, see Resource Tags. If you're not sure whether to apply tags, skip this option or ask an administrator. You can apply tags later.
    8. Select Create.
    9. To confirm that Resource Manager can access the server URL using the provided authentication information, select the configuration source provider to open its details page, and then select Validate connection.

  • Use the oci resource-manager configuration-source-provider create-bitbucket-cloud-email-api-token-provider command and required parameters to create a configuration source provider from Bitbucket Cloud.

    oci resource-manager configuration-source-provider create-bitbucket-cloud-email-api-token-provider --api-endpoint <Bitbucket_Cloud_service_endpoint> --secret-id <secret_OCID> --email-address <atlassian_account_email>

    For a complete list of parameters and values for CLI commands, see the Command Line Reference for Resource Manager.

  • Run the CreateConfigurationSourceProvider operation to create a configuration source provider from Bitbucket Cloud.

    For an example of the configSourceProviderType part of the request, see CreateBitbucketCloudEmailApiTokenConfigurationSourceProviderDetails Reference.