Batch Adding Tags to a Shared File System
Function
This API is used to batch add tags to a shared file system.
A shared file system can have a maximum of 10 tags.
The keys of multiple tags added to a shared file system must be unique.
This API is idempotent. If the key to be added has already been added to the shared file system, the tag is updated.
URI
- POST /v2/{project_id}/sfs/{share_id}/tags/action
- Parameter description
Parameter
Mandatory
Type
Description
project_id
Yes
String
Specifies the project ID of the operator. For details about how to obtain the project ID, see Obtaining a Project ID.
share_id
Yes
String
Specifies the ID of the shared file system.
Request Header
The operation message header is the same as that of a common request. For details, see Table 3.
Request
- Parameter description
Parameter
Mandatory
Type
Description
action
Yes
String
Specifies the operation identifier. Possible values are create and delete. Use create to batch add tags to a specified shared file system.
tags
No
Array of resource_tags
Specifies the tag list.
This parameter is mandatory when the tenant permission is used. For the op_service permission, choose either this field or sys_tags.
sys_tags
No
Array of resource_tags
Specifies the system tag list.
This field is available only to the op_service permission. Choose either this field or tags.
Only one resource_tag structure key, _sys_enterprise_project_id, is used in TMS calls.
The value is ID or 0. Value 0 indicates the default enterprise project.
- Description of field resource_tag
Parameter
Mandatory
Type
Description
key
Yes
String
Specifies the tag key. The value can contain a maximum of 36 characters. The key cannot be left blank and cannot contain non-printable ASCII characters (0-31) or the following characters: =*<>\,|/
value
Yes
String
Specifies the tag value. The value contains a maximum of 43 characters and can be an empty string. It cannot contain non-printable ASCII characters (0-31) or the following characters: =*<>\,|/
- Example request
Status Codes
- Normal
- Abnormal
Status Code
Description
400 Bad Request
Invalid value.
401 Unauthorized
Authentication failed.
403 Forbidden
Access to the requested page is forbidden.
404 Not Found
The requested resource was not found.
500 Internal Server Error
The request is not completed because of a service error.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot