Public cloud APIs comply with the RESTful API design principles. REST-based Web services are organized into resources. Each resource is identified by one or more Uniform Resource Identifiers (URIs). An application accesses a resource based on the resource's Unified Resource Locator (URL). A URL is usually in the following format: https://Endpoint/uri. In the URL, uri indicates the resource path, that is, the API access path.
Public cloud APIs use HTTPS as the transmission protocol. Requests/Responses are transmitted by using JSON messages, with media type represented by Application/json.
For details about how to use APIs, see API Usage Guidelines.
diff --git a/docs/tms/api-ref/en-us_topic_0056765935.html b/docs/tms/api-ref/en-us_topic_0056765935.html
index 9c9993879..e26180d26 100644
--- a/docs/tms/api-ref/en-us_topic_0056765935.html
+++ b/docs/tms/api-ref/en-us_topic_0056765935.html
@@ -33,7 +33,7 @@
Yes
|
-
List<predefine_tag_request>
+ | Array of objects
|
Specifies the tag list.
For details, see Table 2.
@@ -42,35 +42,35 @@
-predefine_tag_request field description
-Table 2 Parameter descriptionName
+tags field description
+Table 2 Parameter descriptionName
|
-Mandatory
+ | Mandatory
|
-Type
+ | Type
|
-Description
+ | Description
|
|---|
-key
+ | key
|
-Yes
+ | Yes
|
-String
+ | String
|
-Specifies the key.
-It cannot be left blank and can contain a maximum of 36 Unicode characters. Can contain only digits, letters, hyphens (-), and underscores (_).
+ | Specifies the key.
+It cannot be left blank and can contain a maximum of 36 Unicode characters. Only digits, letters, hyphens (-), and underscores (_) are allowed.
|
-value
+ | value
|
-Yes
+ | Yes
|
-String
+ | String
|
-Specifies the value.
-Each value contains a maximum of 43 Unicode characters and can be an empty string. Can contain only digits, letters, hyphens (-), and underscores (_).
+ | Specifies the value.
+Each value contains a maximum of 43 Unicode characters and can be an empty string. Only digits, letters, hyphens (-), and underscores (_) are allowed.
|
@@ -98,9 +98,9 @@
-Status CodesSee Status Code.
+
-
diff --git a/docs/tms/api-ref/en-us_topic_0056765936.html b/docs/tms/api-ref/en-us_topic_0056765936.html
index 31f3e822d..a0f8f4559 100644
--- a/docs/tms/api-ref/en-us_topic_0056765936.html
+++ b/docs/tms/api-ref/en-us_topic_0056765936.html
@@ -22,7 +22,7 @@
String
|
- Key
+ | Specifies the key.
Supports fuzzy search and is case insensitive. If this parameter value contains non-URL-safe characters, it must be URL encoded.
|
@@ -32,7 +32,7 @@
String
|
- Value
+ | Specifies the value.
Supports fuzzy search and is case insensitive. If this parameter value contains non-URL-safe characters, it must be URL encoded.
|
@@ -79,10 +79,10 @@
String
|
Specifies the sorting method of the order_field field.
-The value can be (case sensitive):
+The method can be (case sensitive):
- asc: ascending order
- desc: descending order
-Only one of the preceding values can be selected.
-If this parameter is not transferred, the default value is desc.
+Only one of the preceding sorting methods can be selected.
+If this parameter is not specified, the default value is desc.
|
@@ -103,7 +103,7 @@
tags
|
-List<predefine_tag>
+ | Array of objects
|
Specifies the tag list.
For details, see Table 3.
@@ -127,7 +127,7 @@
|
Table 3 Parameter descriptionName
|
Type
@@ -141,7 +141,7 @@
| String
|
Specifies the key.
-It cannot be left blank and can contain a maximum of 36 Unicode characters. Can contain only digits, letters, hyphens (-), and underscores (_).
+It cannot be left blank and can contain a maximum of 36 Unicode characters. Only digits, letters, hyphens (-), and underscores (_) are allowed.
|
|---|
value
@@ -149,7 +149,7 @@
| String
|
Specifies the value.
-Each value contains a maximum of 43 Unicode characters and can be an empty string. Can contain only digits, letters, hyphens (-), and underscores (_).
+Each value contains a maximum of 43 Unicode characters and can be an empty string. Only digits, letters, hyphens (-), and underscores (_) are allowed.
|
update_time
@@ -181,9 +181,9 @@
}
-Status CodesSee Status Code.
+
-
diff --git a/docs/tms/api-ref/en-us_topic_0057939857.html b/docs/tms/api-ref/en-us_topic_0057939857.html
index cae10f3ca..d7e5a85ac 100644
--- a/docs/tms/api-ref/en-us_topic_0057939857.html
+++ b/docs/tms/api-ref/en-us_topic_0057939857.html
@@ -1,6 +1,6 @@
- Error Code Description
+ Error Codes
Function DescriptionIf the returned status code of a TMS API is 400, the customized error information will also be returned. This section describes the meaning of each TMS error code.
Response FormatSTATUS CODE 400
@@ -10,297 +10,324 @@
}
Error Code Description
- Module
+Status Code
|
-HTTP Status Code
+ | Error Code
|
-Error Code
+ | Error Message
|
-Description
+ | Description
|
-Error Message
- |
-Measure
+ | Solution
|
|---|
-Public
+ | 500
|
-500
+ | TMS.0001
|
-TMS.0001
+ | System error.
|
-System error
+ | System error.
|
-System error.
- |
-Contact technical support.
+ | Contact technical support.
|
-400
+ | 400
|
-TMS.0002
+ | TMS.0002
|
-Invalid request from the client
+ | Bad request.
|
-Bad request.
+ | Invalid request from the client.
|
-Enter correct parameters.
+ | Enter valid parameters.
|
-401
+ | 401
|
-TMS.0003
+ | TMS.0003
|
-Authentication fails or the valid authentication information is not provided.
+ | The user is unauthorized.
|
-The user is unauthorized.
+ | Authentication fails or the valid authentication information is not provided.
|
-Check whether the username or password for obtaining the token is correct.
+ | Check whether the username or password for obtaining the token is correct.
|
-403
+ | 403
|
-TMS.0004
+ | TMS.0004
|
-The authentication information is incorrect or the service invoker does not have sufficient permissions.
+ | You do not have permissions to perform the operation.
|
-You do not have permissions to perform the operation.
+ | The authentication information is incorrect or the service invoker does not have sufficient permissions.
|
-Check whether the username, password, or the user permissions for obtaining the token are correct.
+ | Check whether the username, password, or the user permissions for obtaining the token are correct.
|
-404
+ | 404
|
-TMS.0005
+ | TMS.0005
|
-The requested resource cannot be found.
+ | The resources requested cannot be found.
|
-The resources requested cannot be found.
+ | The requested resource cannot be found.
|
-Provide a correct resource ID.
+ | Enter a valid resource ID.
|
-403
+ | 403
|
-TMS.0006
+ | TMS.0006
|
-The numbers of requests are too many.
+ | The request is Too much, try again later.
|
-The request is Too much, try again later.
+ | The numbers of requests are too many.
|
-Reduce the number of concurrent requests or wait for a retry.
+ | Reduce the number of concurrent requests or try again later.
|
-400
+ | 400
|
-TMS.0007
+ | TMS.0007
|
-Limit is invalid.
+ | Limit is invalid.
|
-Limit is invalid.
+ | Limit is invalid.
|
-Enter a correct Limit value.
+ | Enter a valid Limit value.
|
-400
+ | 400
|
-TMS.0008
+ | TMS.0008
|
-Marker is invalid.
+ | Marker is invalid.
|
-Marker is invalid.
+ | Marker is invalid.
|
-Enter a correct Marker value.
+ | Enter a valid Marker value.
|
-400
+ | 400
|
-TMS.0009
+ | TMS.0009
|
-Key is invalid.
+ | Key is invalid.
|
-Key is invalid.
+ | Key is invalid.
|
-Enter a correct Key value.
+ | Enter a valid Key value.
|
-400
+ | 400
|
-TMS.0010
+ | TMS.0010
|
-Value is invalid.
+ | Value is invalid.
|
-Value is invalid.
+ | Value is invalid.
|
-Enter a correct Value value.
+ | Enter a valid Value value.
|
-400
+ | 400
|
-TMS.0011
+ | TMS.0011
|
-Action is invalid.
+ | Action is invalid.
|
-Action is invalid.
+ | Action is invalid.
|
-Enter a correct Action value.
+ | Enter a valid Action value.
|
-400
+ | 400
|
-TMS.0012
+ | TMS.0012
|
-Tags is an empty array.
+ | Tags is empty.
|
-Tags is empty.
+ | Tags is left blank.
|
-Enter a correct Tags value.
+ | Specify Tags.
|
-400
+ | 400
|
-TMS.0013
+ | TMS.0013
|
-Elements in Tags are empty.
+ | Empty element in Tags.
|
-Empty element in Tags.
+ | Tags is invalid.
|
-Enter a correct Tags value.
+ | Enter a valid Tags value.
|
-400
+ | 400
|
-TMS.0014
+ | TMS.0014
|
-Values is invalid.
+ | Values is empty.
|
-Values is empty.
+ | Values is invalid.
|
-Enter a correct Values value.
+ | Enter a valid Values value.
|
-Predefine dtag
+ | 400
|
-400
+ | TMS.0016
|
-TMS.1001
+ | Values is too much.
|
-The number of predefined tags exceeds the quota.
+ | The maximum number of values for Values has been exceeded.
|
-The number of predefine tag exceeds the upper limit.
- |
-Reduce the number of predefined tags.
+ | Enter no more than 10 values.
|
-400
+ | 400
|
-TMS.1002
+ | TMS.0017
|
-Old_tag cannot be found.
+ | Offset is invalid.
|
-Old_tag cannot be found.
+ | Offset is invalid.
|
-Check parameter Old_tag.
+ | Enter a valid Offset value.
|
-400
+ | 504
|
-TMS.1003
+ | TMS.0018
|
-New_tag already exists.
+ | Query Time Out.
|
-New_tag already exists.
+ | Query timed out.
|
-Check parameter New-tag.
+ | Try again later.
|
-400
+ | 400
|
-TMS.1004
+ | TMS.1001
|
-Old_tag is empty.
+ | The number of predefine tag exceeds the upper limit.
|
-Old_tag is empty.
+ | The number of predefined tags exceeds the quota.
|
-Ensure that parameter Old_tag is not empty.
+ | Enter no more than 500 predefined tags.
|
-400
+ | 400
|
-TMS.1005
+ | TMS.1002
|
-The key in Old_tag is invalid.
+ | Old_tag cannot be found.
|
-Invalid key in Old_tag.
+ | Old_tag cannot be found.
|
-Check whether the key in Old_tag is valid.
+ | Specify Old_tag.
|
-400
+ | 400
|
-TMS.1006
+ | TMS.1003
|
-The value in Old_tag is invalid.
+ | New_tag already exists.
|
-Invalid value in Old_tag.
+ | New_tag already exists.
|
-Check whether the value in Old_tag is valid.
+ | Enter another value for New-tag.
|
-400
+ | 400
|
-TMS.1007
+ | TMS.1004
|
-New_tag is empty.
+ | Old_tag is empty.
|
-New_tag is empty.
+ | Old_tag is left blank.
|
-Ensure that parameter New_tag is not empty.
+ | Specify Old_tag.
|
-400
+ | 400
|
-TMS.1008
+ | TMS.1005
|
-The key in New_tag is invalid.
+ | Invalid key in Old_tag.
|
-Invalid key in New_tag.
+ | The key in Old_tag is invalid.
|
-Check whether the key in New_tag is valid.
+ | Enter a valid key in Old_tag.
|
-400
+ | 400
|
-TMS.1009
+ | TMS.1006
|
-The value in New_tag is invalid.
+ | Invalid value in Old_tag.
|
-Invalid value in New_tag.
+ | The value in Old_tag is invalid.
|
-Check whether the value in New_tag is valid.
+ | Enter a valid value in Old_tag.
|
-400
+ | 400
|
-TMS.1010
+ | TMS.1007
|
-Order_field is invalid.
+ | New_tag is empty.
|
-Order_field is invalid.
+ | New_tag is left blank.
|
-Check whether parameter Order_field is valid.
+ | Specify New_tag.
|
-400
+ | 400
|
-TMS.1011
+ | TMS.1008
|
-Order_method is invalid.
+ | Invalid key in New_tag.
|
-Order_method is invalid.
+ | The key in New_tag is invalid.
|
-Check whether parameter Order_method is valid.
+ | Enter a valid key in New_tag.
+ |
+
+400
+ |
+TMS.1009
+ |
+Invalid value in New_tag.
+ |
+The value in New_tag is invalid.
+ |
+Enter a valid value in New_tag.
+ |
+
+400
+ |
+TMS.1010
+ |
+Order_field is invalid.
+ |
+Order_field is invalid.
+ |
+Enter a valid Order_field value.
+ |
+
+400
+ |
+TMS.1011
+ |
+Order_method is invalid.
+ |
+Order_method is invalid.
+ |
+Enter a valid Order_method value.
|
diff --git a/docs/tms/api-ref/en-us_topic_0057939858.html b/docs/tms/api-ref/en-us_topic_0057939858.html
index 18b263dce..1d2c51bca 100644
--- a/docs/tms/api-ref/en-us_topic_0057939858.html
+++ b/docs/tms/api-ref/en-us_topic_0057939858.html
@@ -8,52 +8,58 @@
-2018-11-06
+ | 2023-04-07
|
-This release incorporates the following changes:
+ | This release incorporates the following change:
+Added Permissions Policies and Supported Actions.
+ |
+
+2018-11-06
+ |
+This release incorporates the following change:
Accepted in OTC 3.2.
|
2018-09-30
|
-This release incorporates the following changes:
+ | This release incorporates the following change:
Added APIs for querying version information.
|
2018-06-15
|
This release incorporates the following changes:
-Modified the value requirements for Key and Value.
+Modified the requirements for Key and Value.
|
2018-03-30
|
-This release incorporates the following changes:
-Modified the value requirements for Key and Value.
+ | This release incorporates the following change:
+Modified the requirements for Key and Value.
|
2018-03-16
|
-This release incorporates the following changes:
+ | This release incorporates the following change:
Optimized the descriptions of error codes.
|
2017-08-29
|
-This release incorporates the following changes:
-Optimized the URI parameter description in section Creating or Deleting Predefined Tags.
+ | This release incorporates the following change:
+Optimized the URI parameter description in Creating or Deleting Predefined Tags.
|
2017-07-28
|
-This release incorporates the following changes:
+ | This release incorporates the following change:
Modified the sample code.
|
2017-05-26
|
This release incorporates the following changes:
-
+
|
2017-05-05
diff --git a/docs/tms/api-ref/en-us_topic_0060929630.html b/docs/tms/api-ref/en-us_topic_0060929630.html
index 26dc36444..f5756af86 100644
--- a/docs/tms/api-ref/en-us_topic_0060929630.html
+++ b/docs/tms/api-ref/en-us_topic_0060929630.html
@@ -20,7 +20,7 @@
|
Yes
|
-predefine_tag_request
+ | Object
|
Specifies the tag to be modified.
For details, see Table 2.
@@ -30,44 +30,78 @@
|
Yes
|
-predefine_tag_request
+ | Object
|
Specifies the tag that has been modified.
-For details, see Table 2.
+For details, see Table 3.
|
Table 2 Parameter descriptionName
+old_tag field description
+Table 2 Parameter descriptionName
|
-Mandatory
+ | Mandatory
|
-Type
+ | Type
|
-Description
+ | Description
|
|---|
-key
+ | key
|
-Yes
+ | Yes
|
-String
+ | String
|
-Specifies the key.
-It cannot be left blank and can contain a maximum of 36 Unicode characters. Can contain only digits, letters, hyphens (-), and underscores (_).
+ | Specifies the key.
+It cannot be left blank and can contain a maximum of 36 Unicode characters. Only digits, letters, hyphens (-), and underscores (_) are allowed.
|
-value
+ | value
|
-Yes
+ | Yes
|
-String
+ | String
|
-Specifies the value.
-Each value contains a maximum of 43 Unicode characters and can be an empty string. Can contain only digits, letters, hyphens (-), and underscores (_).
+ | Specifies the value.
+Each value contains a maximum of 43 Unicode characters and can be an empty string. Only digits, letters, hyphens (-), and underscores (_) are allowed.
+ |
+
+
+
+ Table 3 Parameter descriptionName
+ |
+Mandatory
+ |
+Type
+ |
+Description
+ |
+
|---|
+
+key
+ |
+Yes
+ |
+String
+ |
+Specifies the key.
+It cannot be left blank and can contain a maximum of 36 Unicode characters. Only digits, letters, hyphens (-), and underscores (_) are allowed.
+ |
+
+value
+ |
+Yes
+ |
+String
+ |
+Specifies the value.
+Each value contains a maximum of 43 Unicode characters and can be an empty string. Only digits, letters, hyphens (-), and underscores (_) are allowed.
|
@@ -92,9 +126,9 @@
-Status CodesSee Status Code.
+
-
diff --git a/docs/tms/api-ref/en-us_topic_0126416752.html b/docs/tms/api-ref/en-us_topic_0126416752.html
index 6cb622c4a..e23c6d53f 100644
--- a/docs/tms/api-ref/en-us_topic_0126416752.html
+++ b/docs/tms/api-ref/en-us_topic_0126416752.html
@@ -1,12 +1,43 @@
Obtaining a Project ID
- A project ID needs to be specified in the URIs of some APIs. Therefore, you need to obtain the project ID before calling APIs. The following procedure describes how to obtain a project ID: - Log in to the management console.
- Click the username and select My Credential from the drop-down list.
On the My Credential page, view project IDs in the project list.
-Figure 1 Viewing project IDs
+ScenariosA project ID is required for some URLs when an API is called. Therefore, you need to obtain a project ID in advance. Two methods are available:
+
+
+ Obtain the Project ID by Calling an APIYou can obtain the project ID by calling the IAM API used to query project information based on the specified criteria.
+ The API used to obtain a project ID is GET https://{Endpoint}/v3/projects. {Endpoint} is the IAM endpoint and can be obtained from Regions and Endpoints.
+ The following is an example response. The value of id is the project ID.
+ {
+ "projects": [
+ {
+ "domain_id": "65382450e8f64ac0870cd180d14e684b",
+ "is_domain": false,
+ "parent_id": "65382450e8f64ac0870cd180d14e684b",
+ "name": "project_name",
+ "description": "",
+ "links": {
+ "next": null,
+ "previous": null,
+ "self": "https://www.example.com/v3/projects/a4a5d4098fb4474fa22cd05f897d6b99"
+ },
+ "id": "a4a5d4098fb4474fa22cd05f897d6b99",
+ "enabled": true
+ }
+ ],
+ "links": {
+ "next": null,
+ "previous": null,
+ "self": "https://www.example.com/v3/projects"
+ }
+}
+
+ Obtain a Project ID from the ConsoleA project ID needs to be specified in the URIs of some APIs. Therefore, you need to obtain the project ID before calling APIs. The following procedure describes how to obtain a project ID: - Log in to the management console.
- Click the username and select My Credentials from the drop-down list.
On the My Credentials page, view project IDs in the project list.
+Figure 1 Viewing project IDs
In multi-project scenarios, expand the region, and obtain your sub-project ID from the Project ID column.
+
diff --git a/docs/tms/api-ref/en-us_topic_0126416865.html b/docs/tms/api-ref/en-us_topic_0126416865.html
index 36f0707d2..c5e82d211 100644
--- a/docs/tms/api-ref/en-us_topic_0126416865.html
+++ b/docs/tms/api-ref/en-us_topic_0126416865.html
@@ -4,14 +4,12 @@
diff --git a/docs/tms/api-ref/en-us_topic_0130578970.html b/docs/tms/api-ref/en-us_topic_0130578970.html
index c796d7d38..413287805 100644
--- a/docs/tms/api-ref/en-us_topic_0130578970.html
+++ b/docs/tms/api-ref/en-us_topic_0130578970.html
@@ -1,6 +1,6 @@
- Status Code
+ Status Codes
- Normal
Returned Value
|
@@ -50,7 +50,7 @@
|---|
403 Forbidden
|
-You are forbidden to access the requested page.
+ | Access to the requested page is denied.
|
404 Not Found
diff --git a/docs/tms/api-ref/en-us_topic_0133313255.html b/docs/tms/api-ref/en-us_topic_0133313255.html
index 581ad1577..cd4434a5e 100644
--- a/docs/tms/api-ref/en-us_topic_0133313255.html
+++ b/docs/tms/api-ref/en-us_topic_0133313255.html
@@ -4,7 +4,7 @@
-- Querying All API Versions
+ - Querying the API Versions
- Querying Details About a Specified TMS API Version
diff --git a/docs/tms/api-ref/en-us_topic_0133313256.html b/docs/tms/api-ref/en-us_topic_0133313256.html
index a14cbec56..486172136 100644
--- a/docs/tms/api-ref/en-us_topic_0133313256.html
+++ b/docs/tms/api-ref/en-us_topic_0133313256.html
@@ -1,6 +1,6 @@
-Querying All API Versions
+Querying the API Versions
FunctionThis API is used to query the versions of all TMS APIs.
URIGET /
@@ -8,8 +8,7 @@
RequestExample request
GET https://{TMS endpoint}/
-
+  Response- Parameter description
Table 1 Parameters in the responseName
|
@@ -66,7 +65,7 @@
String
|
Specifies the version status.
-Possible values are as follows:
+Possible statuses are as follows:
- CURRENT: indicates that the version is the primary version.
- SUPPORTED: indicates that the version is an old version, but it is still supported.
- DEPRECATED: indicates a deprecated version which may be deleted later.
|
|---|
@@ -87,7 +86,7 @@
- Links field description
+
- Links field description
Table 3 Parameter descriptionName
|
Type
@@ -133,9 +132,9 @@
}
-Status CodesSee Status Code.
+
-
diff --git a/docs/tms/api-ref/en-us_topic_0133313257.html b/docs/tms/api-ref/en-us_topic_0133313257.html
index 4648b75a4..caea86915 100644
--- a/docs/tms/api-ref/en-us_topic_0133313257.html
+++ b/docs/tms/api-ref/en-us_topic_0133313257.html
@@ -88,7 +88,7 @@
Specifies the version status.
Possible values are as follows:
-- CURRENT: indicates that the version is the primary version.
- SUPPORTED: indicates that the version is an old version, but it is still supported.
- DEPRECATED: indicates a deprecated version which may be deleted later.
+- CURRENT: indicates that the version is the primary version.
- SUPPORTED: indicates that the version is an old version, but it is still supported.
- DEPRECATED: indicates a deprecated version which may be deleted later.
|
|
|---|
updated
@@ -151,9 +151,9 @@
}
-Status CodesFor details, see Status Code.
+
-
diff --git a/docs/tms/api-ref/en-us_topic_0170638684.html b/docs/tms/api-ref/en-us_topic_0170638684.html
new file mode 100644
index 000000000..c3b15cc9b
--- /dev/null
+++ b/docs/tms/api-ref/en-us_topic_0170638684.html
@@ -0,0 +1,13 @@
+
+
+ Permissions Policies and Supported Actions
+
+
+
diff --git a/docs/tms/api-ref/en-us_topic_0180205868.html b/docs/tms/api-ref/en-us_topic_0180205868.html
new file mode 100644
index 000000000..c5f69ae57
--- /dev/null
+++ b/docs/tms/api-ref/en-us_topic_0180205868.html
@@ -0,0 +1,19 @@
+
+
+ Permissions Policies and Supported Actions
+ This section describes fine-grained permissions management for your TMS. If your account does not need individual IAM users, then you may skip over this section.
+ By default, new IAM users do not have permissions assigned. You need to add a user to one or more groups, and attach permissions policies or roles to these groups. Users inherit permissions from the groups to which they are added and can perform specified operations on cloud services based on the permissions.
+ You can grant users permissions by using roles and policies. Roles are a type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. Policies define API-based permissions for operations on specific resources under certain conditions, allowing for more fine-grained, secure access control of cloud resources.
+ Policy-based authorization is useful if you want to allow or deny the access to an API.
+
+ An account has all of the permissions required to call all APIs, but IAM users must be assigned the required permissions. The permissions required for calling an API are determined by the actions supported by the API. Only users who have been granted permissions allowing the actions can call the API successfully. For example, if an IAM user wants to query predefined tags using an API, the user must have been granted permissions that allow the tms:predefineTags:list action.
+ Supported ActionsOperations supported by a fine-grained policy are specific to APIs. The following are common concepts related to policies:
+ - Permissions: Statements in a policy that allow or deny certain operations.
- APIs: REST APIs that can be called by a user who has been granted specific permissions.
- Actions: Specific operations that are allowed or denied.
- Related actions: Actions on which a specific action depends to take effect. When assigning permissions for the action to a user, you also need to assign permissions for the related actions.
- IAM or enterprise projects: Type of projects for which an action will take effect. Policies that contain actions supporting both IAM and enterprise projects can be used and take effect in both IAM and Enterprise Management. Policies that only contain actions for IAM projects can be used and only take effect for IAM. Administrators can check whether an action supports IAM projects or enterprise projects in the action list. "√" indicates that the action supports the project and "×" indicates that the action does not support the project.
+
+
+
+
diff --git a/docs/tms/api-ref/en-us_topic_0180205869.html b/docs/tms/api-ref/en-us_topic_0180205869.html
new file mode 100644
index 000000000..d5127db28
--- /dev/null
+++ b/docs/tms/api-ref/en-us_topic_0180205869.html
@@ -0,0 +1,103 @@
+
+
+ TMS API Actions
+
+ Table 1 API actionsPermission
+ |
+API
+ |
+Action
+ |
+IAM Project
+ |
+Enterprise Project
+ |
+
|---|
+
+Querying predefined tags
+ |
+GET /v1.0/predefine_tags
+ |
+tms:predefineTags:list
+ |
+√
+ |
+x
+ |
+
+Creating predefined tags
+ |
+POST /v1.0/predefine_tags/action
+ |
+tms:predefineTags:create
+ |
+√
+ |
+x
+ |
+
+Deleting predefined tags
+ |
+POST /v1.0/predefine_tags/action
+ |
+tms:predefineTags:delete
+ |
+√
+ |
+x
+ |
+
+Modifying predefined tags
+ |
+PUT /v1.0/predefine_tags/action
+ |
+tms:predefineTags:update
+ |
+√
+ |
+x
+ |
+
+Querying resource tags
+ |
+GET /v1.0/tags
+ |
+tms:resourceTags:list
+ |
+√
+ |
+x
+ |
+
+Creating tags
+ |
+POST /v1.0/{resource_type}/{resource_id}/tags/action
+ |
+tms:resourceTags:create
+ |
+√
+ |
+x
+ |
+
+Deleting resource tags
+ |
+POST /v1.0/{resource_type}/{resource_id}/tags/action
+ |
+tms:resourceTags:delete
+ |
+√
+ |
+x
+ |
+
+
+
+
+
+
+
diff --git a/docs/tms/api-ref/en-us_topic_0186103096.html b/docs/tms/api-ref/en-us_topic_0186103096.html
deleted file mode 100644
index be3464af9..000000000
--- a/docs/tms/api-ref/en-us_topic_0186103096.html
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
- Obtaining the Domain-Level Token
-
-Content-Type: application/json
-
-{
- "auth": {
- "identity": {
- "methods": [
- "password"
- ],
- "password": {
- "user": {
- "name": "username",
- "password": "********",
- "domain": {
- "name": "domainname"
- }
- }
- }
- },
- "scope": {
- "domain": {
- "id": "xxxxxxxxxxxxxxxxxx"
- }
- }
- }
-}
-
-
-
diff --git a/docs/tms/api-ref/public_sys-resources/icon-arrowdn.gif b/docs/tms/api-ref/public_sys-resources/icon-arrowdn.gif
index 84eec9be2..379428032 100644
Binary files a/docs/tms/api-ref/public_sys-resources/icon-arrowdn.gif and b/docs/tms/api-ref/public_sys-resources/icon-arrowdn.gif differ
diff --git a/docs/tms/api-ref/public_sys-resources/icon-arrowrt.gif b/docs/tms/api-ref/public_sys-resources/icon-arrowrt.gif
index 39583d168..6aaaa11c2 100644
Binary files a/docs/tms/api-ref/public_sys-resources/icon-arrowrt.gif and b/docs/tms/api-ref/public_sys-resources/icon-arrowrt.gif differ
|
|
|
|---|
|
|---|
| |
|---|
|