You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/build-your-software-catalog/sync-data-to-catalog/git/bitbucket/bitbucket-cloud/_bitbucket_cloud_one_time_docker_parameters.mdx
|`OCEAN__INTEGRATION__CONFIG__BITBUCKET_WORKSPACE_TOKEN`| The workspace token used to query authenticate with your Bitbucket Cloud account|| ✅ |
3
+
|`OCEAN__INTEGRATION__CONFIG__BITBUCKET_WORKSPACE_TOKEN`| The workspace token(s) for the Bitbucket Cloud account (can be a single token or comma-separated string of multiple tokens)|| ✅ |
4
4
|`OCEAN__INTEGRATION__CONFIG__BITBUCKET_WORKSPACE`| The workspace you want to retrieve git objects from || ✅ |
5
5
|`OCEAN__INTEGRATION__CONFIG__BITBUCKET_USERNAME`| The username used to authenticate with your Bitbucket Cloud account || ✅ |
6
6
|`OCEAN__INTEGRATION__CONFIG__BITBUCKET_APP_PASSWORD`| The app password used to authenticate with your Bitbucket Cloud account || ✅ |
Copy file name to clipboardExpand all lines: docs/build-your-software-catalog/sync-data-to-catalog/git/bitbucket/bitbucket-cloud/installation.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,16 +35,16 @@ This page details how to install Port's Bitbucket Cloud integration (powered by
35
35
36
36
:::tip Use of dedicated accounts and tokens
37
37
38
-
We recommend using workspace tokens from accounts dedicated to the integration, as this will provide a more secure and scalable solution.
38
+
We recommend using multiple workspace tokens for the integration, as this will provide a more secure and scalable solution. Using multiple workspace tokens helps distribute the load and avoid rate limiting issues. You can provide multiple workspace tokens as a comma-separated string in the configuration.
39
39
40
-
Different credentials from the same Bitbucket account share the same rate limits, which can cause issues when using the integration in a large organization. Using dedicated workspace tokens helps manage rate limits more effectively.
40
+
If you are using the username and app password, we recommend using a dedicated account for the integration, as different credentials from the same Bitbucket account share the same rate limits, which can cause issues when using the integration in a large organization.
41
41
:::
42
42
43
43
The integration requires either a workspace token or an app password with username to authenticate with your Bitbucket Cloud account. You can create a workspace token by following the steps [here](https://support.atlassian.com/bitbucket-cloud/docs/workspace-access-tokens/) or an app password by following [these steps](https://support.atlassian.com/bitbucket-cloud/docs/app-passwords/).
44
44
45
45
The token or app password should have `read` permission scope for each of the supported resources you want to ingest into Port and a `read` and `write` permission scope for the webhooks.
46
46
47
-
We recommend using workspace tokens when possible, as they provide better security and are easier to manage than app passwords.
47
+
We recommend using multiple workspace tokens when possible, as they provide better security, are easier to manage than app passwords, and help avoid rate limiting issues by distributing requests across different tokens.
48
48
49
49
## Deploy the integration
50
50
@@ -180,7 +180,7 @@ This table summarizes the available parameters for the installation.
180
180
| `integration.config.bitbucketUsername` | The username of the Bitbucket Cloud account | ✅ |
181
181
| `integration.config.bitbucketWorkspace` | The workspace of the Bitbucket Cloud account | ✅ |
182
182
| `integration.config.bitbucketAppPassword` | The app password of the Bitbucket Cloud account | ✅ |
183
-
| `integration.config.bitbucketWorkspaceToken`| The workspace token of the Bitbucket Cloud account | ✅ |
183
+
| `integration.config.bitbucketWorkspaceToken`| The workspace token(s) for the Bitbucket Cloud account (can be a single token or comma-separated string of multiple tokens) | ✅ |
184
184
| `integration.config.webhookSecret` | The secret used to verify the webhook requests | ❌ |
185
185
| `scheduledResyncInterval` | The number of minutes between each resync | ❌ |
186
186
| `initializePortResources` | Default true, When set to true the integration will create default blueprints and the port App config Mapping | ❌ |
0 commit comments