Status Code
Table 7 describes the status code.
diff --git a/docs/css/api-ref/css_03_0031.html b/docs/css/api-ref/css_03_0031.html index f3cdd640..2be7bdec 100644 --- a/docs/css/api-ref/css_03_0031.html +++ b/docs/css/api-ref/css_03_0031.html @@ -64,7 +64,7 @@String
Time when a snapshot is created every day. Snapshots can only be created on the hour. The time format is the time followed by the time zone, specifically, HH:mm z. In the format, HH:mm refers to the hour time and z refers to the time zone, for example, 00:00 GMT+08:00 and 01:00 GMT+08:00.
+Time when a snapshot is created every day. Snapshots can only be created on the hour. The time format is the time followed by the time zone, specifically, HH:mm z. In the format, HH:mm refers to the hour time and z refers to the time zone, for example, 00:00 GMT+08:00 and 01:00 GMT+02:00.
keepday
@@ -104,7 +104,7 @@POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/ea244205-d641-45d9-9dcb-ab2236bcd07e/index_snapshot/policy
{
"prefix":"snapshot",
- "period":"16:00 GMT+08:00",
+ "period":"16:00 GMT+02:00",
"keepday":7,
"enable":"true"
}
diff --git a/docs/css/api-ref/css_03_0032.html b/docs/css/api-ref/css_03_0032.html
index 82b9c960..ea75e487 100644
--- a/docs/css/api-ref/css_03_0032.html
+++ b/docs/css/api-ref/css_03_0032.html
@@ -116,7 +116,7 @@
{
"keepday":2,
- "period":"16:00 GMT+08:00",
+ "period":"16:00 GMT+02:00",
"prefix":"snapshot",
"bucket":"es-backup",
"basePath": "css_repository/tests",
diff --git a/docs/css/api-ref/css_03_0034.html b/docs/css/api-ref/css_03_0034.html
index 284cf531..c548bbf8 100644
--- a/docs/css/api-ref/css_03_0034.html
+++ b/docs/css/api-ref/css_03_0034.html
@@ -244,7 +244,7 @@
String
Engine version number.
+Engine version number.
{
"backups": [
{
- "created": "2018-03-07T07:34:47",
+ "created": "2021-03-07T07:34:47",
"datastore": {
"type": "elasticsearch",
- "version": "*.*.*"
+ "version": "7.6.2"
},
"description": "",
"id": "e29d99c1-3d19-4ea4-ae8d-f252df76cbe9",
@@ -268,7 +268,7 @@
"clusterName": "Es-xfx",
"name": "snapshot-002",
"status": "COMPLETED",
- "updated": "2018-03-07T07:40:12",
+ "updated": "2021-03-07T07:40:12",
"backupType": "1",
"backupMethod": "manual",
"backupExpectedStartTime": null,
@@ -277,17 +277,17 @@
"indices": ".kibana,website2",
"totalShards": 6,
"failedShards": 0,
- "version": "6.2.3",
+ "version": "7.6.2",
"restoreStatus": "success",
"startTime": 1520408087099,
"endTime": 1520408412219,
"bucketName": "obs-b8ed"
},
{
- "created": "2018-03-06T15:42:37",
+ "created": "2021-03-06T15:42:37",
"datastore": {
"type": "elasticsearch",
- "version": "6.2.3"
+ "version": "7.6.2"
},
"description": "",
"id": "29a2254e-947f-4463-b65a-5f0b17515fae",
@@ -295,7 +295,7 @@
"clusterName": "Es-xfx",
"name": "snapshot-001",
"status": "COMPLETED",
- "updated": "2018-03-06T15:48:04",
+ "updated": "2021-03-06T15:48:04",
"backupType": "1",
"backupMethod": "manual",
"backupExpectedStartTime": null,
@@ -304,7 +304,7 @@
"indices": ".kibana",
"totalShards": 1,
"failedShards": 0,
- "version": "6.2.3",
+ "version": "7.6.2",
"restoreStatus": "none",
"startTime": 1520350957275,
"endTime": 1520351284357,
diff --git a/docs/css/api-ref/css_03_0040.html b/docs/css/api-ref/css_03_0040.html
index 250ba57c..142f59e7 100644
--- a/docs/css/api-ref/css_03_0040.html
+++ b/docs/css/api-ref/css_03_0040.html
@@ -10,10 +10,6 @@
- Obtaining a Project ID and Name
- - Common Request Parameters
-
- - Common Response Parameters
- - Status Code
- Error Code
diff --git a/docs/css/api-ref/css_03_0056.html b/docs/css/api-ref/css_03_0056.html index 3be17b7c..214baefb 100644 --- a/docs/css/api-ref/css_03_0056.html +++ b/docs/css/api-ref/css_03_0056.html @@ -1,7 +1,7 @@Supported Cluster Versions
-In CSS, Elasticsearch 7.6.2 and 7.9.3 and Kibana 7.6.2 and 7.9.3 are supported.
+In CSS, Elasticsearch 7.6.2, 7.9.3 and 7.10.2 and Kibana 7.6.2, 7.9.3 and 7.10.2 are supported.
diff --git a/docs/css/api-ref/css_03_0071.html b/docs/css/api-ref/css_03_0071.html index ede35016..c1c8c0e2 100644 --- a/docs/css/api-ref/css_03_0071.html +++ b/docs/css/api-ref/css_03_0071.html @@ -2,7 +2,7 @@Obtaining a Project ID and Name
A project ID or project name is required in some API requests. You need to obtain the project ID and name before calling an API.
-- - \ No newline at end of file diff --git a/docs/css/api-ref/css_03_0078.html b/docs/css/api-ref/css_03_0078.html index b338a1c6..685cd66c 100644 --- a/docs/css/api-ref/css_03_0078.html +++ b/docs/css/api-ref/css_03_0078.html @@ -104,35 +104,35 @@Obtaining a Project ID and Name from the Console
- Log in to the console.
- In the upper right corner of the page, click the username and choose My Credentials from the drop-down list. The My Credentials page is displayed.
- In the project list, view the Project ID and Project Name.Figure 1 Viewing the project ID and name+
Obtaining a Project ID and Name from the Console
- Log in to the console.
- In the upper right corner of the page, click the username and choose My Credentials from the drop-down list. The My Credentials page is displayed.
- In the project list, view the Project ID and Project Name.Figure 1 Viewing the project ID and name
Obtaining a Project ID by Calling an API
The API for obtaining a project ID is GET https://{iam-endpoint}/v3/projects. {iam-endpoint} indicates the endpoint of IAM, which can be obtained from Endpoints.
@@ -38,10 +38,3 @@
Status Code
Table 4 describes the status code.
-Table 4 Status code Status Code
+Table 4 Status code Status Code
Message
+Message
Description
+Description
400
+400
BadRequest
+BadRequest
Invalid request.
-The client should not repeat the request without modifications.
+Invalid request.
+The client should not repeat the request without modifications.
404
+404
NotFound
+NotFound
The requested resource cannot be found.
-The client should not repeat the request without modifications.
+The requested resource cannot be found.
+The client should not repeat the request without modifications.
200
+200
OK
+OK
The request is processed successfully.
+The request is processed successfully.
Status Code
Table 4 describes the status code.
-Table 4 Status code Status Code
+Table 4 Status code Status Code
Message
+Message
Description
+Description
400
+400
BadRequest
+BadRequest
Invalid request.
-The client should not repeat the request without modifications.
+Invalid request.
+The client should not repeat the request without modifications.
404
+404
NotFound
+NotFound
The requested resource cannot be found.
-The client should not repeat the request without modifications.
+The requested resource cannot be found.
+The client should not repeat the request without modifications.
200
+200
OK
+OK
The request is processed successfully.
+The request is processed successfully.
Status Code
Table 4 describes status codes.
-Table 4 Status code Status Code
+Table 4 Status code Status Code
Encoding
+Encoding
Description
+Description
400
+400
BadRequest
+BadRequest
Invalid request.
-Do not retry the request before modification.
+Invalid request.
+Do not retry the request before modification.
404
+404
NotFound
+NotFound
The requested resource cannot be found.
-Do not retry the request before modification.
+The requested resource cannot be found.
+Do not retry the request before modification.
204
+204
OK
+OK
The request is processed successfully.
+The request is processed successfully.
Deleting Specified Cluster Tags
+Deleting Specified Cluster Tags
Function
This API is used to delete specified cluster tags.
URI
DELETE /v1.0/{project_id}/css-cluster/{cluster_id}/tags/{key}@@ -22,7 +22,6 @@String
Project ID
-cluster_id
@@ -58,35 +57,35 @@Status Code
Table 2 describes status codes.
-Table 2 Status code Status Code
+Table 2 Status code Status Code
Encoding
+Encoding
Description
+Description
400
+400
BadRequest
+BadRequest
Invalid request.
-Do not retry the request before modification.
+Invalid request.
+Do not retry the request before modification.
404
+404
NotFound
+NotFound
The requested resource cannot be found.
-Do not retry the request before modification.
+The requested resource cannot be found.
+Do not retry the request before modification.
204
+204
OK
+OK
The request is processed successfully.
+The request is processed successfully.
String
Project ID
-cluster_id
@@ -87,35 +86,35 @@Status Code
Table 3 describes status codes.
-Table 3 Status code Status Code
+Table 3 Status code Status Code
Encoding
+Encoding
Description
+Description
400
+400
BadRequest
+BadRequest
Invalid request.
-Do not retry the request before modification.
+Invalid request.
+Do not retry the request before modification.
404
+404
NotFound
+NotFound
The requested resource cannot be found.
-Do not retry the request before modification.
+The requested resource cannot be found.
+Do not retry the request before modification.
204
+204
OK
+OK
The request is processed successfully.
+The request is processed successfully.
-Request Methods
HTTP-based request methods, which are also called operations or actions, specify the type of operations that you are requesting.
- GET: requests the server to return specified resources.
- PUT: requests the server to update specified resources.
- POST: requests the server to add resources or perform special operations.
- DELETE: requests the server to delete specified resources, for example, an object.
- HEAD: requests a server resource header.
- PATCH: requests the server to update partial content of a specified resource. If the target resource does not exist, PATCH may create a resource.
If POST is displayed in the URI of the API for obtaining a user token, the request is as follows:
--POST https://{iam-endpoint}/v3/auth/tokens+POST https://{iam-endpoint}/v3/auth/tokens- - \ No newline at end of file diff --git a/docs/css/api-ref/public_sys-resources/icon-arrowdn.gif b/docs/css/api-ref/public_sys-resources/icon-arrowdn.gif index 84eec9be..37942803 100644 Binary files a/docs/css/api-ref/public_sys-resources/icon-arrowdn.gif and b/docs/css/api-ref/public_sys-resources/icon-arrowdn.gif differ diff --git a/docs/css/api-ref/public_sys-resources/icon-arrowrt.gif b/docs/css/api-ref/public_sys-resources/icon-arrowrt.gif index 39583d16..6aaaa11c 100644 Binary files a/docs/css/api-ref/public_sys-resources/icon-arrowrt.gif and b/docs/css/api-ref/public_sys-resources/icon-arrowrt.gif differRequest Header
You can also add additional fields to a request, such as the fields required by a specified URI or an HTTP method. For example, add Content-Type that defines a request body type to request for the authentication information.
-Common request headers are as follows:
-- Content-Type: specifies the request body type or format. This field is mandatory and its default value is application/json.
- X-Auth-Token: specifies the user token, which is optional. This field is mandatory for token-based authentication. X-Auth-Token is the value of x-subject-token returned in response to the API used to obtain a user token.-
In addition to supporting authentication using tokens, APIs support authentication using the access key ID (AK)/secret access key (SK), which uses SDKs to sign a request. During the signing, the Authorization (signature authentication information) and X-Sdk-Date (time when a request is sent) headers are automatically added to the request. For more details, see Authentication Using AK/SK.
-
The API used to obtain a user token does not require authentication. Therefore, only the Content-Type field needs to be added to requests for calling the API. An example of such requests is as follows:
-POST https://{iam-endpoint}/v3/auth/tokens +Request Header
You can also add additional fields to a request, such as the fields required by a specified URI or an HTTP method. For example, add Content-Type that defines a request body type to request for the authentication information.
+Table 2 lists common request header fields.
+ ++
+Table 2 Common request headers Parameter
+Mandatory
+Description
+Content-Type
+Yes
+Message body type (or format). You are advised to use the default value application/json.
+X-Auth-Token
+No (Mandatory for token-based authentication)
+User token.
+User token is the response to the API for obtaining a user token (only this API does not require authentication). After the request is processed, the value of X-Subject-Token in the response header (Header) is the token value.
+X-Language
+No
+Request language
+The API used to obtain a user token does not require authentication. Therefore, only the Content-Type field needs to be added to requests for calling the API. An example of such requests is as follows:
+POST https://{iam-endpoint}/v3/auth/tokens Content-Type: application/jsonRequest Body
A request body conveys information other than the request header and is generally sent in a structured format defined by the request header field Content-Type.
diff --git a/docs/css/api-ref/iam_02_0511.html b/docs/css/api-ref/iam_02_0511.html index 1a8512d5..e39fac05 100644 --- a/docs/css/api-ref/iam_02_0511.html +++ b/docs/css/api-ref/iam_02_0511.html @@ -7,7 +7,7 @@Response Header
A response header corresponds to a request header, for example, Content-Type.
Figure 1 shows the response header for the API of obtaining a user token, where x-subject-token is the desired user token. Then, you can use the token to authenticate the calling of other APIs.
- +Response Body
A response body is generally returned in a structured format, corresponding to the Content-Type in the response header, and is used to transfer content other than the response header.
The following shows part of the response body for the API of obtaining a user token.
@@ -37,10 +37,3 @@
