Can't run atlassian/trigger-pipeline pipe with the existing BITBUCKET_ACCESS_TOKEN

Alexander Lavrentyev

Hello!

Starting from July'10, 2023 can't run "atlassian/trigger-pipeline" pipe with the existing BITBUCKET_ACCESS_TOKEN. 

Error: 

<span>Status: Downloaded newer image for bitbucketpipelines/trigger-pipeline:5.1.3</span>

<span>&#10006; API request failed with status 401. Check your account and app password and try again.</span>

Token was revoked and I've got the same result. And status of token using is "never". Looks like it's trying to use"BITBUCKET_USERNAME" and "BITBUCKET_APP_PASSWORD" instead of "BITBUCKET_ACCESS_TOKEN". 

Pipe is the following:

- step: &project-name
    name: Deploy Project-name
script:
      - pipe: atlassian/trigger-pipeline:5.1.3
variables:
BITBUCKET_ACCESS_TOKEN: "$INTERNAL_PIPELINE_TOKEN"
          REPOSITORY: "repository-name"
          CUSTOM_PIPELINE_NAME: deploy-to-dev
WAIT: "true"
          PIPELINE_VARIABLES: >
            [{
              "key": "Stand",
              "value": "$Stand"
            }]

 

Token permissions: Pipelines Write, Repositories Read

Variable exists in the pipe (env): 

--env=BITBUCKET_ACCESS_TOKEN="$INTERNAL_PIPELINE_TOKEN" \

Alexander Lavrentyev

Resolved.

It was incorrect value of token in workspace vars.