Replace Bitbucket Teams by Workspaces until Oct 14

[christianspecht]

https://developer.atlassian.com/cloud/bitbucket/bitbucket-api-teams-deprecation

• Deadline: October 14, 2020

• The concept of a team is going away. It is replaced for the most part by workspaces. The key difference being that teams could act as an account used to authenticate and gain access to Bitbucket. Workspaces are simple content containers.

• Previously, you could get a list of repositories via /2.0/teams/{username}/repositories or /2.0/repositories/{team} which returned the same list. For workspaces, there is only one endpoint, /2.0/repositories/{workspace}

TODO:

• If users need to do something different (like putting a account_id instead of the username into the config), mention this in the docs as soon as possible and show a warning similar to the one in #40

[christianspecht]

api/2.0/users will completely be removed:

Support for accessing repository information via the user's account_id will end when we remove support for the /users and /teams API endpoints later this year. Going forward the best way to retrieve any repository information is to use the workspace_id or the UUID. The account_id is and will be the best way to identify a specific user.

(source)

[christianspecht]

https://developer.atlassian.com/cloud/bitbucket/bitbucket-api-changes-workspaces/

Users are able to separately define a username and workspace ID. The username is used to authenticate over SSH or HTTPS using the Git command line client. The workspace ID is used to form repository URL paths.

You should review your integration’s code to determine if assumptions have been made that repository URLs are of the form {repo.owner.username}/{repo.slug}. If your code works this way it will continue to operate correctly for users whose username and workspace ID match. This is the default case, and will be the majority of users.