Thanks to #1365, BitBucket Cloud Access Token has been supported with env DANGER_BITBUCKETCLOUD_REPO_ACCESSTOKEN.
However, this feature doesn't work currently because of the following issues.
1. Some logics uses the wrong env name DANGER_BITBUCKETCLOUD_REPOSITORY_ACCESSTOKEN.
Because of this issue, need to set both DANGER_BITBUCKETCLOUD_REPO_ACCESSTOKEN and DANGER_BITBUCKETCLOUD_REPOSITORY_ACCESSTOKEN to use this feature.
To fix this, changed the env name in the code.
2. Fails to fetch account UUID due to permission limitation.
Thanks to #1365, BitBucket Cloud Access Token has been supported with env
DANGER_BITBUCKETCLOUD_REPO_ACCESSTOKEN
.However, this feature doesn't work currently because of the following issues.
1. Some logics uses the wrong env name
DANGER_BITBUCKETCLOUD_REPOSITORY_ACCESSTOKEN
.Because of this issue, need to set both
DANGER_BITBUCKETCLOUD_REPO_ACCESSTOKEN
andDANGER_BITBUCKETCLOUD_REPOSITORY_ACCESSTOKEN
to use this feature. To fix this, changed the env name in the code.2. Fails to fetch account UUID due to permission limitation.
According to https://support.atlassian.com/bitbucket-cloud/docs/repository-access-token-permissions/, Bitbucket Repository Access Token doesn't have permission to access account information which needs to fetch account UUID. And this issue causes the following error.
To avoid this error, allowed to use
DANGER_BITBUCKETCLOUD_UUID
env with Access Token.