X-User-Profile
@@ -96,45 +97,45 @@
Response ParametersStatus code: 200
- Table 4 Response body parametersParameter
+Table 4 Response body parametersParameter
|
-Type
+ | Type
|
-Description
+ | Description
|
|---|
-members
+ | members
|
-Array of Member objects
+ | Array of Member objects
|
-Response parameters of adding a backup share member
+ | Response parameters of adding a backup share member
|
-count
+ | count
|
-Integer
+ | Integer
|
-Number of share members that the backup is shared to
+ | Number of share members that the backup is shared to
|
Table 5 MemberParameter
+Table 5 MemberParameter
|
-Type
+ | Type
|
-Description
+ | Description
|
|---|
-status
+ | status
|
-String
+ | String
|
-Backup sharing status
+ | Backup sharing status
Enumeration values:
pending
accepted
@@ -142,53 +143,53 @@
|
-created_at
+ | created_at
|
-String
+ | String
|
-Backup sharing time, for example, 2020-02-05T10:38:34.209782
+ | Backup sharing time, for example, 2020-02-05T10:38:34.209782
|
-updated_at
+ | updated_at
|
-String
+ | String
|
-Update time, for example, 2020-02-05T10:38:34.209782
+ | Update time, for example, 2020-02-05T10:38:34.209782
|
-backup_id
+ | backup_id
|
-String
+ | String
|
-Backup ID
+ | Backup ID
|
-image_id
+ | image_id
|
-String
+ | String
|
-ID of the image created by using the accepted shared backup
+ | ID of the image created by using the accepted shared backup
|
-dest_project_id
+ | dest_project_id
|
-String
+ | String
|
-ID of the project with which the backup is shared
+ | ID of the project with which the backup is shared
|
-vault_id
+ | vault_id
|
-String
+ | String
|
-ID of the vault where the shared backup is stored
+ | ID of the vault where the shared backup is stored
|
-id
+ | id
|
-String
+ | String
|
-ID of the shared record
+ | ID of the shared record
|
@@ -234,7 +235,7 @@
diff --git a/docs/cbr/api-ref/AddVaultResource.html b/docs/cbr/api-ref/AddVaultResource.html
index 438aa0ab0..9f0d5229d 100644
--- a/docs/cbr/api-ref/AddVaultResource.html
+++ b/docs/cbr/api-ref/AddVaultResource.html
@@ -1,7 +1,7 @@
Associating Resources
-FunctionThis API is used to associate resources with a vault.
+ FunctionThis API is used to associate resources with a vault.
URIPOST /v3/{project_id}/vaults/{vault_id}/addresources
@@ -54,7 +54,8 @@
String
|
- User token The token 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.
+ | User token
+The token 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.
|
@@ -162,19 +163,19 @@
Response ParametersStatus code: 200
- Table 6 Response body parametersParameter
+Table 6 Response body parametersParameter
|
-Type
+ | Type
|
-Description
+ | Description
|
|---|
-add_resource_ids
+ | add_resource_ids
|
-Array of strings
+ | Array of strings
|
-List of resource IDs that have been added
+ | List of resource IDs that have been added
|
@@ -220,7 +221,7 @@
diff --git a/docs/cbr/api-ref/AssociateVaultPolicy.html b/docs/cbr/api-ref/AssociateVaultPolicy.html
index 51bc2ae4c..557059a9c 100644
--- a/docs/cbr/api-ref/AssociateVaultPolicy.html
+++ b/docs/cbr/api-ref/AssociateVaultPolicy.html
@@ -1,7 +1,7 @@
Applying a Policy to a Vault
-FunctionThis API is used to apply a policy to a vault.
+ FunctionThis API is used to apply a policy to a vault.
URIPOST /v3/{project_id}/vaults/{vault_id}/associatepolicy
@@ -54,7 +54,8 @@
String
|
- User token The token 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.
+ | User token
+The token 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.
|
@@ -86,45 +87,45 @@
Response ParametersStatus code: 200
- Table 4 Response body parametersParameter
+Table 4 Response body parametersParameter
|
-Type
+ | Type
|
-Description
+ | Description
|
|---|
-associate_policy
+ | associate_policy
|
-VaultPolicyResp object
+ | VaultPolicyResp object
|
-Details of applying a policy to a vault
+ | Details of applying a policy to a vault
|
Table 5 VaultPolicyRespParameter
+Table 5 VaultPolicyRespParameter
|
-Type
+ | Type
|
-Description
+ | Description
|
|---|
-policy_id
+ | policy_id
|
-String
+ | String
|
-Configured policy ID
+ | Configured policy ID
|
-vault_id
+ | vault_id
|
-String
+ | String
|
-Vault ID for configuring the policy ID
+ | Vault ID for configuring the policy ID
|
@@ -167,7 +168,7 @@
diff --git a/docs/cbr/api-ref/BatchCreateAndDeleteVaultTags.html b/docs/cbr/api-ref/BatchCreateAndDeleteVaultTags.html
index 765f4fd5b..a93a6d950 100644
--- a/docs/cbr/api-ref/BatchCreateAndDeleteVaultTags.html
+++ b/docs/cbr/api-ref/BatchCreateAndDeleteVaultTags.html
@@ -1,7 +1,14 @@
Batch Adding or Deleting Tags of a Vault
-FunctionThis API is used to batch add or delete tags for a specified instance. TMS uses this API to manage service resource tags. A resource can have a maximum of 20 tags. This API is idempotent. If there are duplicate keys in the request body when you add tags, an error is reported. If a to-be-added tag has the same key as an existing tag, the tag will be added and will overwrite the existing tag. When deleting tags, duplicate keys are allowed. When deleting tags, if some tags do not exist, the deletion is considered to be successful by default. The character set of the tags will not be verified. A key and a value can each consist of up to 127 and 255 characters. When you delete tags, the tags structure cannot be missing, and the key cannot be left blank or be an empty string.
+ FunctionThis API is used to batch add or delete tags for a specified instance.
+ TMS uses this API to manage service resource tags.
+ A resource can have a maximum of 20 tags.
+ This API is idempotent.
+ If there are duplicate keys in the request body when you add tags, an error is reported.
+ If a to-be-added tag has the same key as an existing tag, the tag will be added and will overwrite the existing tag.
+ When deleting tags, duplicate keys are allowed.
+ When deleting tags, if some tags do not exist, the deletion is considered to be successful by default. The character set of the tags will not be verified. A key and a value can each consist of up to 127 and 255 characters. When you delete tags, the tags structure cannot be missing, and the key cannot be left blank or be an empty string.
Response ParametersStatus code: 400
- |
|---|
|
|---|
|
|---|
|
|---|
|
|---|
|