Querying Repository Groups with Create Permission in a Project
Function
Query repository groups with the create permission in a project.
URI
GET /v4/{project_id}/manageable-groups
Parameter | Mandatory | Type | Description |
|---|---|---|---|
project_id | Yes | String | Project ID. |
scope | No | String | Resource type. This value can be group (repository group) or repository. |
offset | No | Integer | Offset. |
limit | No | Integer | Limit. |
Request Parameters
Parameter | Mandatory | Type | Description |
|---|---|---|---|
X-Auth-Token | Yes | String | User token. It can be obtained by calling the IAM API used to obtain a user token. The value of X-Subject-Token in the response header is the user token. |
Response Parameters
Status code: 200
Parameter | Type | Description |
|---|---|---|
full_name | String | Repository group full name. |
id | Integer | Repository group ID. |
name | String | Repository group name. |
Status code: 401
Parameter | Type | Description |
|---|---|---|
error_code | String | Response status code. |
error_msg | String | Response error information. |
Example Requests
GET https://{endpoint}/v4/{project_id}/manageable-groups Example Responses
Status code: 200
{
[
"full_name": " TG2 / dmz1",
"id": 2111688350,
"name": "dmz1"
]
} Status code: 401
{
"error_code": "DEV.00000003"
"error_msg": "Authentication information expired"
} Status Code
Status Code | Description |
|---|---|
200 | OK |
401 | Unauthorized |
Error code.
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.

