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

Update locations.md

Browse Source 
The purpose of this change is to highlight the style of API access token required to enable the Bitbucket Cloud integration as it was not previously clear. The existing error will not distinguish between an Atlassian Account key(which wont work) and a Bitbucket App Password(which will.

Signed-off-by: John Kriter <john.r.kriter@accenture.com>
This commit is contained in:
John Kriter
2023-10-18 14:24:21 -06:00
committed by GitHub
parent 4996c0d0c3
commit c814a3fbdd
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/integrations/bitbucketCloud/locations.md
+2
View File
@@ -25,6 +25,8 @@ integrations:
> 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 used for this is type [App Password](https://support.atlassian.com/bitbucket-cloud/docs/app-passwords/). 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.