-
Suggestion
-
Resolution: Done
We're using the Bitbucket REST API for automation, and in some cases use endpoints from the v1 API, since (somewhat surprisingly) v2 of the API doesn't comprise everything that's contained in v1.
Now I've discovered that v1 is deprecated and will be disabled at the end of the year (see https://developer.atlassian.com/cloud/bitbucket/deprecation-notice-v1-apis/), and according to that document there is no equivalent to the group-privileges endpoint in v2, so it looks like that part of our automation would then simply stop working.
Thus, please include group privilege management functionality in v2 of the Bitbucket REST API.
- relates to
-
BCLOUD-20367 Add pipeline config variables to v2 workspaces API resource
- Closed
-
-
- Closed
-
-
- Closed
-
- Gathering Interest
- mentioned in
-
Page Failed to load
[BCLOUD-17103] Bitbucket REST API v2 is incomplete
We are currently working on 2.0 CRUD APIs for repository permissions:
- Create
- Read
- Update
- Delete
This will support both Groups and Users at the repository level. This is a pre-cursor for adding support for Project level permissions as well with similar CRUD APIs at that level next year.
When we release the new 2.0 repository permission APIs we will announce a new deprecation timeline for the remaining 1.0 APIs (/groups and /group-privileges). Until the end of that period the 1.0 APIs will continue to function as they always have.
Thanks,
Patrick
+1, We need this badly!
Case: We have many projects, with many repositories (main project, sub-modules) under it.
Each project has one or more senior developers that manage the project and should be able to change repository settings without being an admin of the whole company or team. Managing this manually for each repository is a pain.
Do all the votes and watchers from the other ticket get moved to this one?
I wonder why the later ticket with fewer comments, fewer votes and fewer watchers was selected as the main ticket?
I think we closed both tickets by mistake as duplicates of each other.
Why this is closed with no word of comment? the 2.0 API is incomplete 
+1 We need this as well.
Having this feature improves security because we can use automation scripts to monitor and add/remove users as needed. I'm not sure why they're breaking existing software.
We recently released changed to the Bitbucket Cloud 2.0 REST API, which allows a simple way to automate all Create, Read, Update and Delete (CRUD) operations on repository permissions for both groups and users.
https://developer.atlassian.com/cloud/bitbucket/new-repo-permission-apis/