Deleting a Repository Group
Function
Delete a repository group.
URI
DELETE /v4/{project_id}/groups/{group_id}
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
project_id |
Yes |
String |
Project ID. |
|
group_id |
Yes |
Integer |
Repository group ID. |
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: 202
|
Parameter |
Type |
Description |
|---|---|---|
|
Group test1group1test2 was scheduled for deletion. |
string |
Repository group full name. test1 indicates the first level, and test2 indicates the second level of the repository group. The returned result varies with the actual situation. |
Status code: 401
|
Parameter |
Type |
Description |
|---|---|---|
|
error_code |
String |
Response error code. |
|
error_msg |
String |
Response error information. |
Example Requests
DELETE https://{endpoint}/v4/{project_id}/groups/{group_id}
Example Responses
Status code: 202
{
"Group \u0027group1\u0027 was scheduled for deletion.",
}
Status code: 401
Unauthorized
{
"error_code": "DEV.00000003",
"error_msg": "Authentication information expired"
}
Status Code
|
Status Code |
Description |
|---|---|
|
202 |
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.
