Querying Function Tags
Function
This API is used to query function tags.
URI
GET /v2/{project_id}/{resource_type}/{resource_id}/tags
Parameter | Mandatory | Type | Description |
|---|---|---|---|
project_id | Yes | String | Project ID. For details, see Obtaining a Project ID. |
resource_type | Yes | String | Resource type. Enter functions here. |
resource_id | Yes | String | Resource ID, function URN. |
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. |
Content-Type | Yes | String | Message body type (format). |
Response Parameters
Status code: 200
Parameter | Type | Description |
|---|---|---|
tags | Array of KvItem objects | Tag list. |
sys_tags | Array of KvItem objects | System tags. |
Status code: 400
Parameter | Type | Description |
|---|---|---|
error_code | String | Error code. |
error_msg | String | Error message. |
Status code: 401
Parameter | Type | Description |
|---|---|---|
error_code | String | Error code. |
error_msg | String | Error message. |
Status code: 403
Parameter | Type | Description |
|---|---|---|
error_code | String | Error code. |
error_msg | String | Error message. |
Status code: 500
Parameter | Type | Description |
|---|---|---|
error_code | String | Error code. |
error_msg | String | Error message. |
Example Requests
This API is used to query all resource tags.
GET /v2/{project_id}/{resource_type}/{resource_id}/tags Example Responses
Status code: 200
ok
{
"tags" : [ {
"key" : "xxx",
"value" : "yyy"
} ],
"sys_tags" : [ {
"key" : "_sys_enterprise_project_id",
"value" : "5aa119a8-d25b-45a7-8d1b-88e127885635"
} ]
} Status Codes
Status Code | Description |
|---|---|
200 | ok |
400 | Bad request. |
401 | Unauthorized. |
403 | Forbidden. |
500 | Internal server error. |
Error Codes
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
