For the most recent update on ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1), refer to the AWS Health Dashboard. For information on AWS Service migration, see How do I migrate my services to another region?
Issue with AWS Glue Version Control Git Configuration with Bitbucket
Hello,
I am experiencing an issue with configuring AWS Glue to use Bitbucket for version control. Despite providing the necessary permissions and configuring the repository owner, I am unable to list the workspaces in AWS Glue. Below are the details of my configuration and the issue encountered:
Configuration Details:
- Personal Access Token Permissions:
- Workspace membership – read, write
- Projects – write, admin read
- Repositories – read, write, admin, delete
- Repository Owner: i Provided the repository owner
Issue Encountered: When attempting to list the workspaces in AWS Glue, I receive the following message: "no workspace available."
Steps Taken to Troubleshoot:
-
Verified Personal Access Token: I used Postman to make a request to the Bitbucket API endpoint
https://api.bitbucket.org/2.0/workspacesusing the same personal access token. The request was successful, and I was able to list the workspaces without any issues. -
Repository owner: to get the owner of the repository, I made a request on this api with postman https://api.bitbucket.org/2.0/repositories/my-workspace/my-repository then I took the username in the owner attribute of the response
Despite these steps, AWS Glue is unable to retrieve the workspaces. This indicates that the issue might be with the integration between AWS Glue and Bitbucket.
Below is a capture when I inspect the web page with the browser after having entered the configuration information and I try to list the workspaces
Could you please assist in resolving this issue?
Thank you for your assistance.
Best regards,
Abdoulaye Cisse
- Newest
- Most votes
- Most comments
From the documentation:
Bitbucket uses App passwords and not Repository Access Tokens. For more information on App passwords, see App passwords
Have you tried to use the app password?
Relevant content
- asked 2 years ago
Hello thank you for the responsiveness, yes indeed that is what I used (you can check the first screenshot in the question) but despite that I have the problem
Same issue brought me here, following for solution. I also used the App passwords and am still having the same issue mentioned above
I can confirm I see the same issue in my environment. I opened an internal ticket.
Great, thanks again for the quick response. I'm staying tuned for a solution on this matter.
I was able to get this working:
Account - email, read(in addition to the permissions mentioned in the documentation).Repository ownerbe sure to obtain the value ofUsernamefrom your account settings (not theName).Kindly report back if this is working for you and accept the answer if it does.