Skip to content

Commit ec55549

Browse files
committed
docs: update bitbucket cloud docs for api tokens
this commit updates bitbucket cloud docs about replacement of app passwords with api tokens and adds a guide on how to create api token. Signed-off-by: Zaki Shaikh <zashaikh@redhat.com>
1 parent e5302e0 commit ec55549

File tree

4 files changed

+9
-20
lines changed

4 files changed

+9
-20
lines changed

docs/content/docs/install/bitbucket_cloud.md

Lines changed: 9 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -8,26 +8,16 @@ Pipelines-as-Code supports [Bitbucket Cloud](https://bitbucket.org) through a we
88

99
Follow the Pipelines-as-Code [installation](/docs/install/installation) according to your Kubernetes cluster.
1010

11-
## Create Bitbucket Cloud App Password
11+
## Create Bitbucket API Token
1212

13-
Follow this guide to create an app password:
14-
15-
<https://support.atlassian.com/bitbucket-cloud/docs/app-passwords/>
13+
Follow [this guide](https://support.atlassian.com/bitbucket-cloud/docs/create-an-api-token/) to create an API token.
1614

1715
Check these boxes to add the permissions to the token:
1816

19-
- Account: `Email`, `Read`
20-
- Workspace membership: `Read`, `Write`
21-
- Projects: `Read`, `Write`
22-
- Issues: `Read`, `Write`
23-
- Pull requests: `Read`, `Write`
24-
25-
**NOTE:** If you are going to configure webhook through CLI, you must also add additional permission
26-
27-
- Webhooks: `Read and write`
28-
29-
[Refer to this screenshot](/images/bitbucket-cloud-create-secrete.png) to verify
30-
you have properly configured the app password.
17+
- **read:workspace:bitbucket**
18+
- **read:pullrequest:bitbucket**
19+
- **read:repository:bitbucket**
20+
- **write:repository:bitbucket**
3121

3222
Keep the generated token noted somewhere, or otherwise you will have to recreate it.
3323

@@ -121,16 +111,15 @@ $ tkn pac create repo
121111
spec:
122112
url: "https://bitbucket.com/workspace/repo"
123113
git_provider:
124-
user: "yourbitbucketusername"
114+
user: "your_atlassian_email_id"
125115
secret:
126116
name: "bitbucket-cloud-token"
127117
# Set this if you have a different key in your secret
128118
# key: “provider.token“
129119
```
130120

131-
Please note that the workspace name is different from your username. To view your username in the Bitbucket UI, click on the settings icon, navigate to the
132-
Personal Bitbucket Settings, and there you will find your username there, as shown in image below `zakisk-admin` is username:
133-
![GitOps Commits For Comments](/images/bitbucket-cloud-username-settings.png)
121+
Please note that you must use your Bitbucket/Atlassian account email address in the `user` field of the `Repository` CR. To find your email address, click on your profile icon at the top-left corner in the Bitbucket Cloud UI (see image below), go to **Account Settings**, and scroll down to locate your email address.
122+
![Bitbucket Cloud Account Settings](/images/bitbucket-cloud-account-settings.png)
134123

135124
## Bitbucket Cloud Notes
136125

214 KB
Loading
-150 KB
Binary file not shown.
-259 KB
Binary file not shown.

0 commit comments

Comments
 (0)