From 83590bf1cd0619f5912931627dc13523bc51c5dd Mon Sep 17 00:00:00 2001 From: "Wei, Hongmin" Date: Mon, 26 Aug 2024 08:53:04 +0000 Subject: [PATCH] TMS API 0805 Version Reviewed-by: Ziuzko, Alevtina Co-authored-by: Wei, Hongmin Co-committed-by: Wei, Hongmin --- docs/tms/api-ref/ALL_META.TXT.json | 2 +- docs/tms/api-ref/CLASS.TXT.json | 2 +- docs/tms/api-ref/ListProviders.html | 2 +- ...8295281.png => en-us_image_0000001884958205.png} | Bin docs/tms/api-ref/en-us_topic_0056765936.html | 6 +++--- docs/tms/api-ref/en-us_topic_0057939858.html | 10 ++++++++-- docs/tms/api-ref/en-us_topic_0126416752.html | 6 +++--- docs/tms/api-ref/en-us_topic_0133313256.html | 5 +++-- 8 files changed, 20 insertions(+), 13 deletions(-) rename docs/tms/api-ref/{en-us_image_0000001508295281.png => en-us_image_0000001884958205.png} (100%) diff --git a/docs/tms/api-ref/ALL_META.TXT.json b/docs/tms/api-ref/ALL_META.TXT.json index 63daff0c..1360d3c4 100644 --- a/docs/tms/api-ref/ALL_META.TXT.json +++ b/docs/tms/api-ref/ALL_META.TXT.json @@ -61,7 +61,7 @@ "node_id":"en-us_topic_0133313256.xml", "product_code":"tms", "code":"4", - "des":"This API is used to query the versions of all TMS APIs.GET /Example requestParameter descriptionParameters in the responseNameTypeDescriptionversionsArraySpecifies all AP", + "des":"This API is used to query the versions of all TMS APIs.GET /Example requestYou can obtain the TMS endpoints from Regions and Endpoints.Parameter descriptionParameters in ", "doc_type":"api", "kw":"Querying the API Versions,Querying the API Version,API Reference", "search_title":"", diff --git a/docs/tms/api-ref/CLASS.TXT.json b/docs/tms/api-ref/CLASS.TXT.json index 87f9f803..efe07895 100644 --- a/docs/tms/api-ref/CLASS.TXT.json +++ b/docs/tms/api-ref/CLASS.TXT.json @@ -27,7 +27,7 @@ "code":"3" }, { - "desc":"This API is used to query the versions of all TMS APIs.GET /Example requestParameter descriptionParameters in the responseNameTypeDescriptionversionsArraySpecifies all AP", + "desc":"This API is used to query the versions of all TMS APIs.GET /Example requestYou can obtain the TMS endpoints from Regions and Endpoints.Parameter descriptionParameters in ", "product_code":"tms", "title":"Querying the API Versions", "uri":"en-us_topic_0133313256.html", diff --git a/docs/tms/api-ref/ListProviders.html b/docs/tms/api-ref/ListProviders.html index 427bca8b..1abcec0c 100644 --- a/docs/tms/api-ref/ListProviders.html +++ b/docs/tms/api-ref/ListProviders.html @@ -285,7 +285,7 @@ }, { "provider": "nosql", - "provider_i18n_display_name": "GaussDBNoSQL", + "provider_i18n_display_name": "geminidb", "resource_types": [ { "global": false, diff --git a/docs/tms/api-ref/en-us_image_0000001508295281.png b/docs/tms/api-ref/en-us_image_0000001884958205.png similarity index 100% rename from docs/tms/api-ref/en-us_image_0000001508295281.png rename to docs/tms/api-ref/en-us_image_0000001884958205.png diff --git a/docs/tms/api-ref/en-us_topic_0056765936.html b/docs/tms/api-ref/en-us_topic_0056765936.html index 093962f5..4211533e 100644 --- a/docs/tms/api-ref/en-us_topic_0056765936.html +++ b/docs/tms/api-ref/en-us_topic_0056765936.html @@ -92,7 +92,7 @@

Its default value is update_time.

You can choose only one of the three values and based on the value of order_method to sort the remaining two default fields.

For example:

-
  • If order_field is set to update_time, both key and value are sorted in the ascending order.
  • If order_field is set to key, update_time is sorted in the descending order, and value is sorted in the ascending order.
  • If order_field is set to value, update_time is sorted in the descending order, and key is sorted in the ascending order.
  • If order_field is not specified, its default value update_time is taken. In this case, key and value are sorted in the ascending order.
+
  • If order_field is set to update_time, both key and value are sorted in the ascending order.
  • If order_field is set to key, update_time is sorted in the descending order, and value is sorted in the ascending order.
  • If order_field is set to value, update_time is sorted in the descending order, and key is sorted in the ascending order.
  • If order_field is not specified, its default value update_time is taken. In this case, key and value are sorted in the ascending order.

order_method

@@ -153,9 +153,9 @@
  • tags field description
    - - diff --git a/docs/tms/api-ref/en-us_topic_0057939858.html b/docs/tms/api-ref/en-us_topic_0057939858.html index 8298d651..315e67e9 100644 --- a/docs/tms/api-ref/en-us_topic_0057939858.html +++ b/docs/tms/api-ref/en-us_topic_0057939858.html @@ -8,7 +8,13 @@ - + + +
    Table 4 Fields

    Name

    Type

    +

    Type

    Description

    +

    Description

    2023-11-17

    +

    2024-08-01

    +

    This release incorporates the following change:

    +

    Updated the service name, GaussDB NoSQL, to GeminiDB in Querying Services Supported by TMS.

    +

    2023-11-17

    This release incorporates the following change:

    Modified the example request for the API Query Tag Values.

    @@ -71,7 +77,7 @@

    2018-03-30

    This release incorporates the following change:

    -

    Modified the requirements for Key and Value.

    +

    Modified the requirements for Key and Value.

    2018-03-16

    diff --git a/docs/tms/api-ref/en-us_topic_0126416752.html b/docs/tms/api-ref/en-us_topic_0126416752.html index f118318a..b92f4c27 100644 --- a/docs/tms/api-ref/en-us_topic_0126416752.html +++ b/docs/tms/api-ref/en-us_topic_0126416752.html @@ -2,10 +2,10 @@

    Obtaining a Project ID

    Scenarios

    A 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 API

    You 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 API for obtaining 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": [
@@ -32,7 +32,7 @@
 }

    Obtain a Project ID from the Console

    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:
    1. Log in to the management console.
    2. 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
      +
      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_0133313256.html b/docs/tms/api-ref/en-us_topic_0133313256.html index dc5d943e..7e90691d 100644 --- a/docs/tms/api-ref/en-us_topic_0133313256.html +++ b/docs/tms/api-ref/en-us_topic_0133313256.html @@ -8,7 +8,8 @@

    Request

    Example request

    GET https://{TMS endpoint}/
    -
    +

    You can obtain the TMS endpoints from Regions and Endpoints.

    +

    Response

    • Parameter description
      @@ -86,7 +87,7 @@
      Table 1 Parameters in the response

      Name
      -
    • Links field description +
    • Links field description
      Table 3 Parameter description

      Name

      Type