Replacement for listing all user repositories

Roman Chametka

Hello,

This is a followup to this question regarding endpoint deprecation in  CHANGE-2770.

I see that two new API endpoints have been released, but there doesn't seem to be a replacement for the <strong>GET /repositories</strong> endpoint.

I understand that support for cross-workspace APIs has ended, but I'm wondering if there's an API endpoint that can tell me which repositories a user is a collaborator on (i.e., they have direct access to the repository but not the workspace itself)? Or is being a collaborator not something that's going to be supported going forward?

Previously, the repositories endpoint helped us make this distinction. We need this information to determine which workspaces contain repositories the user collaborates on.

Additionally, I wanted to confirm that there are no plans to release an endpoint that will allow a user to list all repositories they have access to across workspaces?

Thank you.

Ben

Hi @Roman Chametka 

I raised your questions with our engineering teams and I was informed that you've had a conversation with them directly regarding these queries. 

For other community users who are curious about the concerns above - I will share the response from our engineering team below:

1. We will not release an equivalent cross-workspace GET /2.0/repositories API. Changes to our architecture is what necessitated the deprecation of cross-workspace APIs in the first place, and we cannot support them going forward. The only "cross-workspace" endpoint we can support going forward is the new /2.0/user/workspaces 
2. It is not possible for a Bitbucket user to have a granted permission on a repository, but not also be a member of the repository's workspace. It is a requirement for a user to have member permission on a workspace, to have any permission on resources within that workspace. (Note that public repos are visible to any user even without granted permission. But for all repos, a permission grant requires workspace membership)
3. There are no concrete plans to provide a direct workspace-scoped replacement to GET /2.0/user/permissions/repositories , that specifically shows the requesting user's permission level on repositories. Unfortunately as of now, the current workaround (ie, using the role filter with /2.0/repositories) is the best we can provide.

Cheers!

- Ben (Bitbucket Cloud Support)