Updating Tags of an EVS Resource by Key (Deprecated)

Function

This API is used to update tags of an EVS resource by key.

This API has been deprecated. Use another API. For details, see Batch Adding Tags for the Specified EVS Disk.

Constraints

• A tag is composed of a key-value pair.
  • Key:
    • Must be unique for each resource.
    • Can contain a maximum of 36 characters.
    • Can contain only digits, letters, hyphens (-), and underscores (_).
  • Value:
    • Can contain a maximum of 43 characters.
    • Can contain only digits, letters, hyphens (-), and underscores (_).

• A maximum of 10 tags can be created for an EVS resource.

URI

• URI format

  PUT /v2/{project_id}/os-vendor-tags/{resource_type}/{resource_id}/{key}

• Parameter description

  Parameter	Mandatory	Description
  project_id	Yes	Specifies the project ID.
  resource_type	Yes	Specifies the resource type. The value can be volumes, snapshots, or backups.
  resource_id	Yes	Specifies the resource ID.
  key	Yes	Specifies the key of the tag.

Request

• Parameter description

  Parameter	Type	Mandatory	Description
  tag	Object	Yes	Specifies the key-value pair of the tag.

• Description of the request header parameter

  Parameter	Type	Mandatory	Description
  Content-Type	Object	Yes	Specifies the type. The value can be application/json.

• Example request

  {
      "tag": {
          "key_0": "value_0"
      }
  }

Response

• Parameter description

  Parameter	Type	Description
  tag	Object	Specifies the key-value pair of the tag.

• Example response

  {
      "tag": {
          "key_0": "value_0"
      }
  }

  or

  {
      "error": {
        ta  "message": "XXXX", 
          "code": "XXX"
      }
  }

  In the preceding example, error indicates a general error, for example, badRequest or itemNotFound. An example is provided as follows:

  {
      "badRequest": {
          "message": "Request body and URI mismatch", 
          "code": 400
      }
  }

Status Codes

• Normal

  200

Error Codes

For details, see Error Codes.