diff --git a/docs/vpcep/api-ref/.placeholder b/docs/vpcep/api-ref/.placeholder
deleted file mode 100644
index e69de29bb..000000000
diff --git a/docs/vpcep/api-ref/ALL_META.TXT.json b/docs/vpcep/api-ref/ALL_META.TXT.json
index b3861bc5c..41e899290 100644
--- a/docs/vpcep/api-ref/ALL_META.TXT.json
+++ b/docs/vpcep/api-ref/ALL_META.TXT.json
@@ -33,7 +33,7 @@
"uri":"vpcep_06_0101.html",
"product_code":"vpcep",
"code":"4",
- "des":"This API is used to query versions of VPCEP APIs.GET /Example requestGET https://{endpoint}/GET https://{endpoint}/ParametersResponse parametersParameterTypeDescriptionve",
+ "des":"This API is used to query versions of VPCEP APIs.v2 cannot be used.GET /Example requestGET https://{endpoint}/GET https://{endpoint}/ParametersResponse parametersParamete",
"doc_type":"api",
"kw":"Querying Versions of VPCEP APIs,Version Management,API Reference",
"title":"Querying Versions of VPCEP APIs",
@@ -43,7 +43,7 @@
"uri":"vpcep_06_0102.html",
"product_code":"vpcep",
"code":"5",
- "des":"This API is used to query the version of a specified VPCEP API.GET /{version}ParametersRequest parametersParameterMandatoryTypeDescriptionversionNoStringSpecifies the ver",
+ "des":"This API is used to query the version of a specified VPCEP API.GET /{version}ParametersRequest parameterParameterMandatoryTypeDescriptionversionNoStringSpecifies the vers",
"doc_type":"api",
"kw":"Querying the Version of a Specified VPCEP API,Version Management,API Reference",
"title":"Querying the Version of a Specified VPCEP API",
@@ -63,7 +63,7 @@
"uri":"vpcep_06_0201.html",
"product_code":"vpcep",
"code":"7",
- "des":"This API is used to create a VPC endpoint service. Other users can create a VPC endpoint to connect to the endpoint service.This API is an asynchronous interface. If it i",
+ "des":"This API is used to create a VPC endpoint service. Other users can create a VPC endpoint to connect to the endpoint service.This API is asynchronous. If it is successfull",
"doc_type":"api",
"kw":"Creating a VPC Endpoint Service,APIs for Managing VPC Endpoint Services,API Reference",
"title":"Creating a VPC Endpoint Service",
@@ -73,17 +73,17 @@
"uri":"vpcep_06_0202.html",
"product_code":"vpcep",
"code":"8",
- "des":"This API is used to query details of a VPC endpoint service.GET /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}Table 1 describes the required parameters.",
+ "des":"This API is used to query details about a VPC endpoint service.GET /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}Table 1 describes parameters in this UR",
"doc_type":"api",
- "kw":"Querying Details of a VPC Endpoint Service,APIs for Managing VPC Endpoint Services,API Reference",
- "title":"Querying Details of a VPC Endpoint Service",
+ "kw":"Querying Details About a VPC Endpoint Service,APIs for Managing VPC Endpoint Services,API Reference",
+ "title":"Querying Details About a VPC Endpoint Service",
"githuburl":""
},
{
"uri":"vpcep_06_0203.html",
"product_code":"vpcep",
"code":"9",
- "des":"This API is used to modify a VPC endpoint service.PUT /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}Table 1 describes the required parameters.Parameter ",
+ "des":"This API is used to modify a VPC endpoint service.PUT /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}Table 1 describes parameters in this URI.URI paramet",
"doc_type":"api",
"kw":"Modifying a VPC Endpoint Service,APIs for Managing VPC Endpoint Services,API Reference",
"title":"Modifying a VPC Endpoint Service",
@@ -93,7 +93,7 @@
"uri":"vpcep_06_0204.html",
"product_code":"vpcep",
"code":"10",
- "des":"This API is used to delete a VPC endpoint service.DELETE /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}Table 1 describes the required parameters.Paramet",
+ "des":"This API is used to delete a VPC endpoint service.This API is asynchronous. If it is successfully invoked, status code 200 is returned, indicating that the request has be",
"doc_type":"api",
"kw":"Deleting a VPC Endpoint Service,APIs for Managing VPC Endpoint Services,API Reference",
"title":"Deleting a VPC Endpoint Service",
@@ -113,7 +113,7 @@
"uri":"vpcep_06_0206.html",
"product_code":"vpcep",
"code":"12",
- "des":"This API is used to query connections of a VPC endpoint service. The marker ID is the unique ID of each connection.GET /v1/{project_id}/vpc-endpoint-services/{vpc_endpoin",
+ "des":"This API is used to query connections of a VPC endpoint service. marker_id is the unique ID of each connection.GET /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_se",
"doc_type":"api",
"kw":"Querying Connections of a VPC Endpoint Service,APIs for Managing VPC Endpoint Services,API Reference",
"title":"Querying Connections of a VPC Endpoint Service",
@@ -133,57 +133,57 @@
"uri":"vpcep_06_0208.html",
"product_code":"vpcep",
"code":"14",
- "des":"This API is used to query the whitelist records of a VPC endpoint service.Your domain ID is in the whitelist of your own VPC endpoint service by default.GET /v1/{project_",
+ "des":"This API is used to query whitelist records of a VPC endpoint service.Your domain ID is in the whitelist of your own VPC endpoint service by default.GET /v1/{project_id}/",
"doc_type":"api",
- "kw":"Querying the Whitelist Records of a VPC Endpoint Service,APIs for Managing VPC Endpoint Services,API",
- "title":"Querying the Whitelist Records of a VPC Endpoint Service",
+ "kw":"Querying Whitelist Records of a VPC Endpoint Service,APIs for Managing VPC Endpoint Services,API Ref",
+ "title":"Querying Whitelist Records of a VPC Endpoint Service",
"githuburl":""
},
{
"uri":"vpcep_06_0209.html",
"product_code":"vpcep",
"code":"15",
- "des":"This API is used to batch add to or delete whitelist records from a VPC endpoint service.Your domain ID is in the whitelist of your own VPC endpoint service by default.PO",
+ "des":"This API is used to batch add or delete whitelist records of a VPC endpoint service.Your domain ID is in the whitelist of your own VPC endpoint service by default.POST /v",
"doc_type":"api",
- "kw":"Batch Adding or Deleting Whitelist Records of a VPC Endpoint Service,APIs for Managing VPC Endpoint ",
- "title":"Batch Adding or Deleting Whitelist Records of a VPC Endpoint Service",
+ "kw":"Batch Adding or Deleting Whitelist Records,APIs for Managing VPC Endpoint Services,API Reference",
+ "title":"Batch Adding or Deleting Whitelist Records",
+ "githuburl":""
+ },
+ {
+ "uri":"vpcep_06_0301.html",
+ "product_code":"vpcep",
+ "code":"16",
+ "des":"This API is used to query public VPC endpoint services. These services are created by operations people and can be visible to and assessed by all users.GET /v1/{project_i",
+ "doc_type":"api",
+ "kw":"Querying Public VPC Endpoint Services,APIs for Managing VPC Endpoint Services,API Reference",
+ "title":"Querying Public VPC Endpoint Services",
+ "githuburl":""
+ },
+ {
+ "uri":"vpcep_06_0302.html",
+ "product_code":"vpcep",
+ "code":"17",
+ "des":"This API is used to query basic information about a target VPC endpoint service. You can use this API to query the target VPC endpoint service to be accessed. This API ca",
+ "doc_type":"api",
+ "kw":"Querying Basic Information About a VPC Endpoint Service,APIs for Managing VPC Endpoint Services,API ",
+ "title":"Querying Basic Information About a VPC Endpoint Service",
"githuburl":""
},
{
"uri":"vpcep_06_0300.html",
"product_code":"vpcep",
- "code":"16",
+ "code":"18",
"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"api",
"kw":"APIs for Managing VPC Endpoints",
"title":"APIs for Managing VPC Endpoints",
"githuburl":""
},
- {
- "uri":"vpcep_06_0301.html",
- "product_code":"vpcep",
- "code":"17",
- "des":"This API is used to query public VPC endpoint services. These services are created by operations people and can be visible to and assessed by all users.GET /v1/{project_i",
- "doc_type":"api",
- "kw":"Querying Public VPC Endpoint Services,APIs for Managing VPC Endpoints,API Reference",
- "title":"Querying Public VPC Endpoint Services",
- "githuburl":""
- },
- {
- "uri":"vpcep_06_0302.html",
- "product_code":"vpcep",
- "code":"18",
- "des":"This API is used to query basic information of a target VPC endpoint service. You can use this API to query the target VPC endpoint service to be accessed. This API can a",
- "doc_type":"api",
- "kw":"Querying Basic Information of a VPC Endpoint Service,APIs for Managing VPC Endpoints,API Reference",
- "title":"Querying Basic Information of a VPC Endpoint Service",
- "githuburl":""
- },
{
"uri":"vpcep_06_0303.html",
"product_code":"vpcep",
"code":"19",
- "des":"This API is used to create a VPC endpoint for accessing a VPC endpoint service.POST /v1/{project_id}/vpc-endpointsTable 1 describes the required parameters.Parameter desc",
+ "des":"This API is used to create a VPC endpoint for accessing a VPC endpoint service.This API is asynchronous. If it is successfully invoked, status code 200 is returned, indic",
"doc_type":"api",
"kw":"Creating a VPC Endpoint,APIs for Managing VPC Endpoints,API Reference",
"title":"Creating a VPC Endpoint",
@@ -193,17 +193,17 @@
"uri":"vpcep_06_0304.html",
"product_code":"vpcep",
"code":"20",
- "des":"This API is used to query details of a VPC endpoint.GET /v1/{project_id}/vpc-endpoints/{vpc_endpoint_id}Table 1 describes the required parameters.Parameter descriptionPar",
+ "des":"This API is used to query details about a VPC endpoint.GET /v1/{project_id}/vpc-endpoints/{vpc_endpoint_id}Table 1 describes parameters in this URI.URI parametersParamete",
"doc_type":"api",
- "kw":"Querying Details of a VPC Endpoint,APIs for Managing VPC Endpoints,API Reference",
- "title":"Querying Details of a VPC Endpoint",
+ "kw":"Querying Details About a VPC Endpoint,APIs for Managing VPC Endpoints,API Reference",
+ "title":"Querying Details About a VPC Endpoint",
"githuburl":""
},
{
"uri":"vpcep_06_0305.html",
"product_code":"vpcep",
"code":"21",
- "des":"This API is used to delete a VPC endpoint.DELETE /v1/{project_id}/vpc-endpoints/{vpc_endpoint_id}For detailed about the parameters, see Table 1.ParametersParameterMandato",
+ "des":"This API is used to delete a VPC endpoint.This API is asynchronous. If it is successfully invoked, status code 200 is returned, indicating that the request has been succe",
"doc_type":"api",
"kw":"Deleting a VPC Endpoint,APIs for Managing VPC Endpoints,API Reference",
"title":"Deleting a VPC Endpoint",
@@ -253,7 +253,7 @@
"uri":"vpcep_06_0501.html",
"product_code":"vpcep",
"code":"26",
- "des":"This API is used to query resources under the tenant using tags.POST /v1/{project_id}/{resource_type}/resource_instances/actionTable 1 describes the required parameters.",
+ "des":"This API is used to query resources of a tenant by tag.POST /v1/{project_id}/{resource_type}/resource_instances/actionTable 1 describes parameters in this URI.URI parame",
"doc_type":"api",
"kw":"Querying Resources by Tag,Tag Function,API Reference",
"title":"Querying Resources by Tag",
@@ -263,17 +263,17 @@
"uri":"vpcep_06_0502.html",
"product_code":"vpcep",
"code":"27",
- "des":"This API is used to batch add or delete tags for a specified VPC endpoint service or VPC endpoint.You can add a maximum of 20 tags to a resource.POST /v1/{project_id}/{r",
+ "des":"This API is used to batch add tags to or delete tags from a specified VPC endpoint service or VPC endpoint.You can add up to 20 tags to a resource.POST /v1/{project_id}/",
"doc_type":"api",
- "kw":"Batch Adding or Deleting Tags of a Specified Resource,Tag Function,API Reference",
- "title":"Batch Adding or Deleting Tags of a Specified Resource",
+ "kw":"Batch Adding Tags to or Deleting Tags from a Specified Resource,Tag Function,API Reference",
+ "title":"Batch Adding Tags to or Deleting Tags from a Specified Resource",
"githuburl":""
},
{
"uri":"vpcep_06_0503.html",
"product_code":"vpcep",
"code":"28",
- "des":"This API is used to obtain tags of resources of a tenant based on the tenant ID and resource type.GET /v1/{project_id}/{resource_type}/tagsTable 1 describes the required",
+ "des":"This API is used to obtain tags of resources of a tenant based on the tenant ID and resource type.GET /v1/{project_id}/{resource_type}/tagsTable 1 describes parameters i",
"doc_type":"api",
"kw":"Querying Tags of a Tenant's Resource,Tag Function,API Reference",
"title":"Querying Tags of a Tenant's Resource",
@@ -283,7 +283,7 @@
"uri":"vpcep_06_0504.html",
"product_code":"vpcep",
"code":"29",
- "des":"The key should be Unicode characters, including only digits, letters, hyphens (-), and underscores (_). It cannot be empty.The value should be Unicode characters, includi",
+ "des":"The key should be Unicode characters and cannot be left blank. Only digits, letters, hyphens (-), underscores, and at signs (@) are allowed.The value should be Unicode ch",
"doc_type":"api",
"kw":"Tag Character Set Specifications,Tag Function,API Reference",
"title":"Tag Character Set Specifications",
@@ -305,8 +305,8 @@
"code":"31",
"des":"NormalReturn values for successful requestsStatus CodeReturned ValueDescription200OKThe results of POST, GET, and PUT operations are returned as expected.204No ContentThe",
"doc_type":"api",
- "kw":"Status Code,Appendix,API Reference",
- "title":"Status Code",
+ "kw":"Status Codes,Appendix,API Reference",
+ "title":"Status Codes",
"githuburl":""
},
{
@@ -315,15 +315,15 @@
"code":"32",
"des":"If an error occurs during API calling, a customized error message will be returned. This section describes the meaning of each status code returned by VPCEP.An error code",
"doc_type":"api",
- "kw":"Error Code,Appendix,API Reference",
- "title":"Error Code",
+ "kw":"Error Codes,Appendix,API Reference",
+ "title":"Error Codes",
"githuburl":""
},
{
- "uri":"vpcep_08_0003_0.html",
+ "uri":"vpcep_08_0003.html",
"product_code":"vpcep",
"code":"33",
- "des":"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 ob",
+ "des":"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 Ca",
"doc_type":"api",
"kw":"Obtaining a Project ID,Appendix,API Reference",
"title":"Obtaining a Project ID",
diff --git a/docs/vpcep/api-ref/CLASS.TXT.json b/docs/vpcep/api-ref/CLASS.TXT.json
index 036cd4ba1..85b09982b 100644
--- a/docs/vpcep/api-ref/CLASS.TXT.json
+++ b/docs/vpcep/api-ref/CLASS.TXT.json
@@ -27,7 +27,7 @@
"code":"3"
},
{
- "desc":"This API is used to query versions of VPCEP APIs.GET /Example requestGET https://{endpoint}/GET https://{endpoint}/ParametersResponse parametersParameterTypeDescriptionve",
+ "desc":"This API is used to query versions of VPCEP APIs.v2 cannot be used.GET /Example requestGET https://{endpoint}/GET https://{endpoint}/ParametersResponse parametersParamete",
"product_code":"vpcep",
"title":"Querying Versions of VPCEP APIs",
"uri":"vpcep_06_0101.html",
@@ -36,7 +36,7 @@
"code":"4"
},
{
- "desc":"This API is used to query the version of a specified VPCEP API.GET /{version}ParametersRequest parametersParameterMandatoryTypeDescriptionversionNoStringSpecifies the ver",
+ "desc":"This API is used to query the version of a specified VPCEP API.GET /{version}ParametersRequest parameterParameterMandatoryTypeDescriptionversionNoStringSpecifies the vers",
"product_code":"vpcep",
"title":"Querying the Version of a Specified VPCEP API",
"uri":"vpcep_06_0102.html",
@@ -54,7 +54,7 @@
"code":"6"
},
{
- "desc":"This API is used to create a VPC endpoint service. Other users can create a VPC endpoint to connect to the endpoint service.This API is an asynchronous interface. If it i",
+ "desc":"This API is used to create a VPC endpoint service. Other users can create a VPC endpoint to connect to the endpoint service.This API is asynchronous. If it is successfull",
"product_code":"vpcep",
"title":"Creating a VPC Endpoint Service",
"uri":"vpcep_06_0201.html",
@@ -63,16 +63,16 @@
"code":"7"
},
{
- "desc":"This API is used to query details of a VPC endpoint service.GET /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}Table 1 describes the required parameters.",
+ "desc":"This API is used to query details about a VPC endpoint service.GET /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}Table 1 describes parameters in this UR",
"product_code":"vpcep",
- "title":"Querying Details of a VPC Endpoint Service",
+ "title":"Querying Details About a VPC Endpoint Service",
"uri":"vpcep_06_0202.html",
"doc_type":"api",
"p_code":"6",
"code":"8"
},
{
- "desc":"This API is used to modify a VPC endpoint service.PUT /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}Table 1 describes the required parameters.Parameter ",
+ "desc":"This API is used to modify a VPC endpoint service.PUT /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}Table 1 describes parameters in this URI.URI paramet",
"product_code":"vpcep",
"title":"Modifying a VPC Endpoint Service",
"uri":"vpcep_06_0203.html",
@@ -81,7 +81,7 @@
"code":"9"
},
{
- "desc":"This API is used to delete a VPC endpoint service.DELETE /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}Table 1 describes the required parameters.Paramet",
+ "desc":"This API is used to delete a VPC endpoint service.This API is asynchronous. If it is successfully invoked, status code 200 is returned, indicating that the request has be",
"product_code":"vpcep",
"title":"Deleting a VPC Endpoint Service",
"uri":"vpcep_06_0204.html",
@@ -99,7 +99,7 @@
"code":"11"
},
{
- "desc":"This API is used to query connections of a VPC endpoint service. The marker ID is the unique ID of each connection.GET /v1/{project_id}/vpc-endpoint-services/{vpc_endpoin",
+ "desc":"This API is used to query connections of a VPC endpoint service. marker_id is the unique ID of each connection.GET /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_se",
"product_code":"vpcep",
"title":"Querying Connections of a VPC Endpoint Service",
"uri":"vpcep_06_0206.html",
@@ -117,23 +117,41 @@
"code":"13"
},
{
- "desc":"This API is used to query the whitelist records of a VPC endpoint service.Your domain ID is in the whitelist of your own VPC endpoint service by default.GET /v1/{project_",
+ "desc":"This API is used to query whitelist records of a VPC endpoint service.Your domain ID is in the whitelist of your own VPC endpoint service by default.GET /v1/{project_id}/",
"product_code":"vpcep",
- "title":"Querying the Whitelist Records of a VPC Endpoint Service",
+ "title":"Querying Whitelist Records of a VPC Endpoint Service",
"uri":"vpcep_06_0208.html",
"doc_type":"api",
"p_code":"6",
"code":"14"
},
{
- "desc":"This API is used to batch add to or delete whitelist records from a VPC endpoint service.Your domain ID is in the whitelist of your own VPC endpoint service by default.PO",
+ "desc":"This API is used to batch add or delete whitelist records of a VPC endpoint service.Your domain ID is in the whitelist of your own VPC endpoint service by default.POST /v",
"product_code":"vpcep",
- "title":"Batch Adding or Deleting Whitelist Records of a VPC Endpoint Service",
+ "title":"Batch Adding or Deleting Whitelist Records",
"uri":"vpcep_06_0209.html",
"doc_type":"api",
"p_code":"6",
"code":"15"
},
+ {
+ "desc":"This API is used to query public VPC endpoint services. These services are created by operations people and can be visible to and assessed by all users.GET /v1/{project_i",
+ "product_code":"vpcep",
+ "title":"Querying Public VPC Endpoint Services",
+ "uri":"vpcep_06_0301.html",
+ "doc_type":"api",
+ "p_code":"6",
+ "code":"16"
+ },
+ {
+ "desc":"This API is used to query basic information about a target VPC endpoint service. You can use this API to query the target VPC endpoint service to be accessed. This API ca",
+ "product_code":"vpcep",
+ "title":"Querying Basic Information About a VPC Endpoint Service",
+ "uri":"vpcep_06_0302.html",
+ "doc_type":"api",
+ "p_code":"6",
+ "code":"17"
+ },
{
"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"product_code":"vpcep",
@@ -141,51 +159,33 @@
"uri":"vpcep_06_0300.html",
"doc_type":"api",
"p_code":"2",
- "code":"16"
- },
- {
- "desc":"This API is used to query public VPC endpoint services. These services are created by operations people and can be visible to and assessed by all users.GET /v1/{project_i",
- "product_code":"vpcep",
- "title":"Querying Public VPC Endpoint Services",
- "uri":"vpcep_06_0301.html",
- "doc_type":"api",
- "p_code":"16",
- "code":"17"
- },
- {
- "desc":"This API is used to query basic information of a target VPC endpoint service. You can use this API to query the target VPC endpoint service to be accessed. This API can a",
- "product_code":"vpcep",
- "title":"Querying Basic Information of a VPC Endpoint Service",
- "uri":"vpcep_06_0302.html",
- "doc_type":"api",
- "p_code":"16",
"code":"18"
},
{
- "desc":"This API is used to create a VPC endpoint for accessing a VPC endpoint service.POST /v1/{project_id}/vpc-endpointsTable 1 describes the required parameters.Parameter desc",
+ "desc":"This API is used to create a VPC endpoint for accessing a VPC endpoint service.This API is asynchronous. If it is successfully invoked, status code 200 is returned, indic",
"product_code":"vpcep",
"title":"Creating a VPC Endpoint",
"uri":"vpcep_06_0303.html",
"doc_type":"api",
- "p_code":"16",
+ "p_code":"18",
"code":"19"
},
{
- "desc":"This API is used to query details of a VPC endpoint.GET /v1/{project_id}/vpc-endpoints/{vpc_endpoint_id}Table 1 describes the required parameters.Parameter descriptionPar",
+ "desc":"This API is used to query details about a VPC endpoint.GET /v1/{project_id}/vpc-endpoints/{vpc_endpoint_id}Table 1 describes parameters in this URI.URI parametersParamete",
"product_code":"vpcep",
- "title":"Querying Details of a VPC Endpoint",
+ "title":"Querying Details About a VPC Endpoint",
"uri":"vpcep_06_0304.html",
"doc_type":"api",
- "p_code":"16",
+ "p_code":"18",
"code":"20"
},
{
- "desc":"This API is used to delete a VPC endpoint.DELETE /v1/{project_id}/vpc-endpoints/{vpc_endpoint_id}For detailed about the parameters, see Table 1.ParametersParameterMandato",
+ "desc":"This API is used to delete a VPC endpoint.This API is asynchronous. If it is successfully invoked, status code 200 is returned, indicating that the request has been succe",
"product_code":"vpcep",
"title":"Deleting a VPC Endpoint",
"uri":"vpcep_06_0305.html",
"doc_type":"api",
- "p_code":"16",
+ "p_code":"18",
"code":"21"
},
{
@@ -194,7 +194,7 @@
"title":"Querying VPC Endpoints",
"uri":"vpcep_06_0306.html",
"doc_type":"api",
- "p_code":"16",
+ "p_code":"18",
"code":"22"
},
{
@@ -225,7 +225,7 @@
"code":"25"
},
{
- "desc":"This API is used to query resources under the tenant using tags.POST /v1/{project_id}/{resource_type}/resource_instances/actionTable 1 describes the required parameters.",
+ "desc":"This API is used to query resources of a tenant by tag.POST /v1/{project_id}/{resource_type}/resource_instances/actionTable 1 describes parameters in this URI.URI parame",
"product_code":"vpcep",
"title":"Querying Resources by Tag",
"uri":"vpcep_06_0501.html",
@@ -234,16 +234,16 @@
"code":"26"
},
{
- "desc":"This API is used to batch add or delete tags for a specified VPC endpoint service or VPC endpoint.You can add a maximum of 20 tags to a resource.POST /v1/{project_id}/{r",
+ "desc":"This API is used to batch add tags to or delete tags from a specified VPC endpoint service or VPC endpoint.You can add up to 20 tags to a resource.POST /v1/{project_id}/",
"product_code":"vpcep",
- "title":"Batch Adding or Deleting Tags of a Specified Resource",
+ "title":"Batch Adding Tags to or Deleting Tags from a Specified Resource",
"uri":"vpcep_06_0502.html",
"doc_type":"api",
"p_code":"25",
"code":"27"
},
{
- "desc":"This API is used to obtain tags of resources of a tenant based on the tenant ID and resource type.GET /v1/{project_id}/{resource_type}/tagsTable 1 describes the required",
+ "desc":"This API is used to obtain tags of resources of a tenant based on the tenant ID and resource type.GET /v1/{project_id}/{resource_type}/tagsTable 1 describes parameters i",
"product_code":"vpcep",
"title":"Querying Tags of a Tenant's Resource",
"uri":"vpcep_06_0503.html",
@@ -252,7 +252,7 @@
"code":"28"
},
{
- "desc":"The key should be Unicode characters, including only digits, letters, hyphens (-), and underscores (_). It cannot be empty.The value should be Unicode characters, includi",
+ "desc":"The key should be Unicode characters and cannot be left blank. Only digits, letters, hyphens (-), underscores, and at signs (@) are allowed.The value should be Unicode ch",
"product_code":"vpcep",
"title":"Tag Character Set Specifications",
"uri":"vpcep_06_0504.html",
@@ -272,7 +272,7 @@
{
"desc":"NormalReturn values for successful requestsStatus CodeReturned ValueDescription200OKThe results of POST, GET, and PUT operations are returned as expected.204No ContentThe",
"product_code":"vpcep",
- "title":"Status Code",
+ "title":"Status Codes",
"uri":"vpcep_08_0001.html",
"doc_type":"api",
"p_code":"30",
@@ -281,17 +281,17 @@
{
"desc":"If an error occurs during API calling, a customized error message will be returned. This section describes the meaning of each status code returned by VPCEP.An error code",
"product_code":"vpcep",
- "title":"Error Code",
+ "title":"Error Codes",
"uri":"vpcep_08_0002.html",
"doc_type":"api",
"p_code":"30",
"code":"32"
},
{
- "desc":"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 ob",
+ "desc":"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 Ca",
"product_code":"vpcep",
"title":"Obtaining a Project ID",
- "uri":"vpcep_08_0003_0.html",
+ "uri":"vpcep_08_0003.html",
"doc_type":"api",
"p_code":"30",
"code":"33"
diff --git a/docs/vpcep/api-ref/en-us_image_0218975120.png b/docs/vpcep/api-ref/en-us_image_0000001508295281.png
similarity index 100%
rename from docs/vpcep/api-ref/en-us_image_0218975120.png
rename to docs/vpcep/api-ref/en-us_image_0000001508295281.png
diff --git a/docs/vpcep/api-ref/public_sys-resources/icon-arrowdn.gif b/docs/vpcep/api-ref/public_sys-resources/icon-arrowdn.gif
index 84eec9be2..379428032 100644
Binary files a/docs/vpcep/api-ref/public_sys-resources/icon-arrowdn.gif and b/docs/vpcep/api-ref/public_sys-resources/icon-arrowdn.gif differ
diff --git a/docs/vpcep/api-ref/public_sys-resources/icon-arrowrt.gif b/docs/vpcep/api-ref/public_sys-resources/icon-arrowrt.gif
index 39583d168..6aaaa11c2 100644
Binary files a/docs/vpcep/api-ref/public_sys-resources/icon-arrowrt.gif and b/docs/vpcep/api-ref/public_sys-resources/icon-arrowrt.gif differ
diff --git a/docs/vpcep/api-ref/vpcep_00_0004.html b/docs/vpcep/api-ref/vpcep_00_0004.html
index a4e7a743c..d0243f98f 100644
--- a/docs/vpcep/api-ref/vpcep_00_0004.html
+++ b/docs/vpcep/api-ref/vpcep_00_0004.html
@@ -8,21 +8,69 @@
-
2021-02-05
+ |
2023-06-13
|
-This issue incorporates the following changes:
+ | This issue incorporates the following changes:
+
+ |
+
+2023-06-08
+ |
+This issue incorporates the following changes:
+- Added a note in Function.
- Modified the descriptions of port_id and server_type in Table 2 and Table 5.
- Modified the descriptions of port_id and server_type in Table 2.
- Modified the descriptions of port_id and server_type in Table 2 and Table 4.
- Modified the descriptions of port_id and server_type in Table 3.
- Modified the description of dns_names in Table 4.
+ |
+
+2023-06-07
+ |
+This issue incorporates the following changes:
+- Modified the description of port_id in Table 2 and Table 5.
- Modified the description of port_id in Table 2.
- Modified the description of port_id in Table 2 and Table 4.
- Modified the description of port_id in Table 3.
- Modified the descriptions of subnet_id, enable_dns, and dns_names in Table 2 and Table 4.
- Modified the descriptions of enable_dns, dns_names, and subnet_id in Table 2.
- Modified the descriptions of enable_dns, dns_names, and subnet_id in Table 3.
+ |
+
+2023-06-06
+ |
+This issue incorporates the following changes:
+- Updated Example response in Querying Versions of VPCEP APIs.
- Modified the description of approval_enabled in Table 2 and Table 5.
- Modified the description of approval_enabled in Table 2.
- Modified the description of approval_enabled in Table 4.
- Modified the description of approval_enabled in Table 3.
- Added description to Table 3.
- Modified the type and description of routetables, and modified the descriptions of whitelist and enable_whitelist in Table 2. Added response parameters specification_name, endpoint_pool_id, and description to Table 4.
- Modified the descriptions of parameters whitelist, enable_whitelist, and routetables and added response parameters description, specification_name, and endpoint_pool_id to Table 2.
- Modified the description of parameters whitelist, enable_whitelist, and routetables in Response and added response parameters description, specification_name, and endpoint_pool_id to Response.
+ |
+
+2023-05-25
+ |
+This issue incorporates the following changes:
+
+ |
+
+2023-04-26
+ |
+This issue incorporates the following changes:
+
+ |
+
+2023-03-06
+ |
+This issue incorporates the following changes:
+- Updated the description of parameter protocol in Table 3 and Table 6.
- Updated the description of parameter protocol in Table 3.
- Updated the description of parameter protocol in Table 3 and Table 5.
- Updated the description of parameter protocol in Table 5.
+ |
+
+2022-10-26
+ |
+This issue incorporates the following changes:
+- Updated the description of parameters port_id, server_type, and tcp_proxy in Table 2.
- Updated the description of parameters port_id, vip_port_id, server_type, status, and tcp_proxy in Table 5. Deleted cidr_type in Table 5.
- Updated the description of parameters port_id, server_type, and tcp_proxy in Table 2.
- Updated the description of parameters port_id and tcp_proxy in Table 2.
- Updated the description of parameters port_id, server_type, and tcp_proxy in Table 4.
- Updated the description of parameter sort_key in Table 2.
- Updated the description of parameters port_id, server_type, and tcp_proxy in Table 3.
- Updated the description of sort_key in Table 2 and adjusted the position of Table 2.
- Updated the description of parameter status in Table 3.
- Added sort_key in URI.
- Updated the description of sort_key in Table 2 and adjusted the position of Table 2.
- Updated the description of parameter created_at in Table 3.
- Updated the description of parameter sort_key in Table 2.
- Updated the name and adjusted the position of Table 2.
- Updated the description of parameter status in Table 4.
- Updated the description of parameter sort_key in Table 2.
- Updated Example request in Querying Resources by Tag.
- Updated Example request in Batch Adding Tags to or Deleting Tags from a Specified Resource.
- Updated Example request in Querying Tags of a Tenant's Resource.
+ |
+
+2021-02-05
+ |
+This issue incorporates the following change:
Supported a maximum of 20 tags for a resource.
|
2020-11-02
|
-This issue incorporates the following changes:
-Optimized request parameter permissions in Batch Adding or Deleting Whitelist Records of a VPC Endpoint Service.
+ | This issue incorporates the following change:
+Optimized request parameter permissions in Batch Adding or Deleting Whitelist Records.
|
2020-07-31
|
-This issue incorporates the following changes:
+ | This issue incorporates the following change:
Changed parameter service_type from "Mandatory" to "Optional" in Creating a VPC Endpoint Service.
|
diff --git a/docs/vpcep/api-ref/vpcep_06_0101.html b/docs/vpcep/api-ref/vpcep_06_0101.html
index 35a278edd..ed9d6063a 100644
--- a/docs/vpcep/api-ref/vpcep_06_0101.html
+++ b/docs/vpcep/api-ref/vpcep_06_0101.html
@@ -1,7 +1,9 @@
Querying Versions of VPCEP APIs
-Function
This API is used to query versions of VPCEP APIs.
+
Function
This API is used to query versions of VPCEP APIs.
+
@@ -118,26 +120,40 @@
-
- Example response
{
- "versions":[
- {
- "updated":"2018-09-30T00:00:00Z",
- "version":"1",
- "min_version":"",
- "status":"CURRENT",
- "id":"v1",
- "links":[
+- Example response
{
+ "versions": [
{
- "href":"https://{vpcep_uri}/v1",
- "type":"application/json",
- "rel":"self"
+ "status": "CURRENT",
+ "id": "v1",
+ "updated": "2018-09-30T00:00:00Z",
+ "version": "1",
+ "links": [
+ {
+ "rel": "self",
+ "href": "https://{vpcep_uri}/v1",
+ "type": "application/json"
+ }
+ ],
+ "min_version": ""
+ },
+ {
+ "status": "CURRENT",
+ "id": "v2",
+ "updated": "2020-03-30T00:00:00Z",
+ "version": "2",
+ "links": [
+ {
+ "rel": "self",
+ "href": "https://{vpcep_uri}/v2",
+ "type": "application/json"
+ }
+ ],
+ "min_version": ""
}
- ]
- }
- ]
+ ]
}
-Status Code
For details about status codes, see Status Code.
+
diff --git a/docs/vpcep/api-ref/vpcep_06_0102.html b/docs/vpcep/api-ref/vpcep_06_0102.html
index 3997abd16..2d9079d1f 100644
--- a/docs/vpcep/api-ref/vpcep_06_0102.html
+++ b/docs/vpcep/api-ref/vpcep_06_0102.html
@@ -6,7 +6,7 @@
Request
- Parameters
-
Table 1 Request parametersParameter
+Table 1 Request parameterParameter
|
Mandatory
|
@@ -32,8 +32,8 @@
- Example request
GET https://{endpoint}/v1
-Response- Parameters
-
Table 2 Response parametersParameter
+Response- Parameter
+
Table 2 Response parameterParameter
|
Type
|
@@ -52,7 +52,7 @@
|---|
-Table 3 VersionModel parametersParameter
+Table 3 VersionModel parametersParameter
|
Type
|
@@ -108,7 +108,7 @@
|---|
-Table 4 VersionLink parametersParameter
+Table 4 VersionLink parametersParameter
|
Type
|
@@ -161,7 +161,7 @@
}
}
-Status CodeFor details about status codes, see Status Code.
+
diff --git a/docs/vpcep/api-ref/vpcep_06_0200.html b/docs/vpcep/api-ref/vpcep_06_0200.html
index 67ea22462..b08377eac 100644
--- a/docs/vpcep/api-ref/vpcep_06_0200.html
+++ b/docs/vpcep/api-ref/vpcep_06_0200.html
@@ -6,7 +6,7 @@
diff --git a/docs/vpcep/api-ref/vpcep_06_0201.html b/docs/vpcep/api-ref/vpcep_06_0201.html
index acbfb7510..004f982ea 100644
--- a/docs/vpcep/api-ref/vpcep_06_0201.html
+++ b/docs/vpcep/api-ref/vpcep_06_0201.html
@@ -1,13 +1,13 @@
Creating a VPC Endpoint Service
- FunctionThis API is used to create a VPC endpoint service. Other users can create a VPC endpoint to connect to the endpoint service.
- This API is an asynchronous interface. If it is successfully invoked, status code 200 is returned, indicating that the request has been successfully delivered. It takes 1 to 2 minutes to create a VPC endpoint service. You can view the creation result by performing operations in Querying Details of a VPC Endpoint Service.
+ FunctionThis API is used to create a VPC endpoint service. Other users can create a VPC endpoint to connect to the endpoint service.
+ This API is asynchronous. If it is successfully invoked, status code 200 is returned, indicating that the request has been successfully delivered. It takes 1 to 2 minutes to create a VPC endpoint service. You can view the creation result by performing operations in Querying Details About a VPC Endpoint Service.
URIPOST /v1/{project_id}/vpc-endpoint-services
- Table 1 describes the required parameters.
- Table 1 Parameter descriptionParameter
+Table 1 describes the parameter in this URI.
+ Table 1 URI parameterParameter
|
Mandatory
|
@@ -19,7 +19,7 @@
Yes
|
-Specifies the project ID. For details about how to obtain the project ID, see Obtaining a Project ID.
+ | Specifies the project ID. For details about how to obtain the project ID, see Obtaining a Project ID.
|
@@ -28,13 +28,13 @@
Request- Parameter description
-
Table 2 Request parametersParameter
+Table 2 Request parametersParameter
|
-Mandatory
+ | Mandatory
|
Type
|
-Description
+ | Description
|
@@ -44,10 +44,10 @@
String
|
-Specifies the ID for identifying the backend resource of the VPC endpoint service. The ID is in the form of the UUID.
+ | Specifies the ID for identifying the backend resource of the VPC endpoint service. The ID is in universally unique identifier (UUID) format.
The values are as follows:
-- If the backend resource is an enhanced load balancer, the value is the ID of the port bound to the private IP address of the load balancer. For details, see response field vip_port_id in Querying Details of a Load Balancer in the Elastic Load Balancing API Reference.
- If the backend resource is an ECS, the value is the NIC ID of the ECS where the VPC endpoint service is deployed. For details, see Querying NICs of an ECS in the Elastic Load Balancing API Reference.
- If the backend resource is a virtual IP address, the value is the NIC ID of the physical server where virtual resources are created.
- NOTE: - To create a VPC endpoint service, the CIDR block of the VPC where the VPC endpoint service is deployed cannot overlap with 198.19.128.0/20.
- The destination address of the custom route in the VPC route table cannot overlap with 198.19.128.0/20.
+ - If the backend resource is a load balancer, the value is the ID of the port bound to the private IP address of the load balancer. For details, see response field port_id in Querying Details of a Load Balancer and Viewing Details of a Load Balancer in the Elastic Load Balancing API Reference.
- If the backend resource is an ECS, the value is the NIC ID of the ECS where the VPC endpoint service is deployed. For details, see port_id in the response in section Querying NICs of an ECS in the Elastic Cloud Server API Reference.
- If the backend resource is a virtual IP address, the value is the port ID of the physical server where virtual resources are created. (This value will be discarded. The LB type is recommended.)
- If the backend resource is a BMS, the value is the NIC ID of the BMS where the VPC endpoint service is deployed. (This value will be discarded. The LB type is recommended.)
+ NOTE: - To create a VPC endpoint service, the CIDR block of the VPC where the VPC endpoint service is deployed cannot overlap with 198.19.128.0/17.
- The destination address of the custom route in the VPC route table cannot overlap with 198.19.128.0/17.
|
@@ -60,15 +60,6 @@
Specifies the ID of the cluster associated with the target VPCEP resource.
|
-vip_port_id
- |
-No
- |
-String
- |
-Specifies the ID of the virtual NIC to which the virtual IP address is bound.
- |
-
service_name
|
No
@@ -76,7 +67,7 @@
| String
|
Specifies the name of the VPC endpoint service. The name can contain a maximum of 16 characters, including letters, digits, underscores (_), and hyphens (-).
-- If you do not specify this parameter, the VPC endpoint service name is in the format: regionName.serviceId.
- If you specify this parameter, the VPC endpoint service name is in the format: regionName.serviceName.serviceId.
+- If you do not specify this parameter, the VPC endpoint service name is in the format: regionName.serviceId.
- If you specify this parameter, the VPC endpoint service name is in the format: regionName+.+serviceName+.+serviceId.
|
vpc_id
@@ -96,7 +87,7 @@
| Boolean
|
Specifies whether connection approval is required.
-- false: indicates that connection approval is not required. The created VPC endpoint is in the Accepted state.
- true: indicates that connection approval is required. The created VPC endpoint is in the Pending acceptance state until the owner of the associated VPC endpoint service approves the connection.
+- false: Connection approval is not required. The created VPC endpoint is in the accepted state.
- true: Connection approval is required. The created VPC endpoint is in the pendingAcceptance state until the owner of the associated VPC endpoint service approves the connection.
The default value is true.
|
@@ -119,7 +110,7 @@
String
|
Specifies the resource type.
-- VM: Select this value if the backend resource is an ECS. Backend resources of this type serve as servers.
- VIP: Select this value if the backend resource is a virtual IP address that functions as a physical server hosting virtual resources.
- LB: Select this value if the backend resource is an enhanced load balancer. Backend resources of this type suit services that receive high access traffic and demand high reliability and disaster recovery (DR) performance.
+- LB: Select this value if the backend resource is a load balancer. Backend resources of this type suit services that receive high access traffic and demand high reliability and disaster recovery (DR) performance.
- VM: Select this value if the backend resource is an ECS. Backend resources of this type serve as servers.
- VIP: Select this value if the backend resource is a virtual IP address. (This value will be discarded. The LB type is recommended.)
- BMS: Select this value if the backend resource is a BMS. (This value will be discarded. The LB type is recommended.)
|
ports
@@ -129,7 +120,7 @@
| Array of objects
|
Lists the port mappings opened to the VPC endpoint service. For details, see Table 3.
-Duplicate port mappings are not allowed in the same VPC endpoint service. If multiple VPC endpoint services share the same port_id value, service ports and terminal ports of all these endpoint services cannot be duplicated when the protocol is the same. A maximum of 200 port mappings can be created at a time.
+Duplicate port mappings are not allowed in the same VPC endpoint service. If multiple VPC endpoint services share the same port_id value, either server_port or protocol, or both server_port and protocol of each VPC endpoint service must be unique. A maximum of 200 port mappings can be created at a time.
|
tcp_proxy
@@ -144,7 +135,7 @@
- Proxy Protocol: The client information is inserted into field tcp payload and transmitted to the server.
This parameter is available only when the server can parse fields tcp option and tcp payload.
The values are as follows:
-- close: indicates that the TOA and Proxy Protocol methods are neither used.
- toa_open: indicates that the TOA method is used.
- proxy_open: indicates that the Proxy Protocol method is used.
- open: indicates that the TOA and Proxy Protocol methods are both used.
+- close: The TOA and Proxy Protocol methods are neither used.
- toa_open: The TOA method is used.
- proxy_open: The Proxy Protocol method is used.
- open: The TOA and Proxy Protocol methods are both used.
- proxy_vni: The TOA Protocol method is not used. Proxy and virtual network ID are used.
The default value is close.
|
@@ -162,13 +153,13 @@
-Table 3 Port mapping parametersParameter
+Table 3 Port parametersParameter
|
Mandatory
|
-Type
+ | Type
|
-Description
+ | Description
|
@@ -198,16 +189,17 @@
String
|
-Specifies the protocol used in port mappings. The protocol can be TCP or UDP. The default protocol is TCP.
+ | Specifies the port mapping protocol. TCP is supported.
+The default value is TCP.
|
-Table 4 ResourceTags parametersParameter
+Table 4 Tags parametersParameter
|
-Mandatory
+ | Mandatory
|
Type
|
@@ -221,7 +213,7 @@
String
|
-Specifies the tag key. A tag key contains a maximum of 36 Unicode characters. This parameter cannot be left blank. It can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
+ | Specifies the tag key. A tag key contains a maximum of 36 Unicode characters. key cannot be left blank. It can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
|
value
@@ -261,11 +253,11 @@
Response- Parameter description
-
Table 5 Response parametersParameter
+Table 5 Response parametersParameter
|
-Type
+ | Type
|
-Description
+ | Description
|
@@ -280,16 +272,8 @@
String
|
-Specifies the ID for identifying the backend resource of the VPC endpoint service. The ID is in the form of the UUID. The values are as follows:
-- If the backend resource is an enhanced load balancer, the value is the ID of the port bound to the private IP address of the load balancer.
- If the backend resource is an ECS, the value is the NIC ID of the ECS where the VPC endpoint service is deployed.
- If the backend resource is a virtual IP address, the value is the NIC ID of the physical server where virtual resources are created.
- |
-
-vip_port_id
- |
-String
- |
-Specifies the ID of the virtual NIC to which the virtual IP address is bound.
-This parameter is returned only when port_id is set to VIP.
+ | Specifies the ID for identifying the backend resource of the VPC endpoint service. The ID is in UUID format. The values are as follows:
+- If the backend resource is a load balancer, the value is the ID of the port bound to the private IP address of the load balancer.
- If the backend resource is an ECS, the value is the NIC ID of the ECS where the VPC endpoint service is deployed.
- If the backend resource is a virtual IP address, the value is the port ID of the physical server where virtual resources are created. (This value will be discarded. The LB type is recommended.)
- If the backend resource is a BMS, the value is the NIC ID of the BMS where the VPC endpoint service is deployed. (This value will be discarded. The LB type is recommended.)
|
service_name
@@ -314,7 +298,7 @@
| String
|
Specifies the resource type.
-- VM: indicates the ECS.
- VIP: indicates the virtual IP address.
- LB: indicates the enhanced load balancer.
+- LB: indicates a load balancer.
- VM: indicates an ECS.
- VIP: indicates a virtual IP address. (This value has been discarded. The LB type is recommended.)
- BMS: indicates a BMS. (This value has been discarded. The LB type is recommended.)
|
vpc_id
@@ -336,7 +320,7 @@
| Boolean
|
Specifies whether connection approval is required.
-- false: indicates that connection approval is not required. The created VPC endpoint is in the Accepted state.
- true: indicates that connection approval is required. The created VPC endpoint is in the Pending acceptance state until the owner of the associated VPC endpoint service approves the connection.
+- false: Connection approval is not required. The created VPC endpoint is in the accepted state.
- true: Connection approval is required. The created VPC endpoint is in the pendingAcceptance state until the owner of the associated VPC endpoint service approves the connection.
|
status
@@ -344,7 +328,7 @@
| String
|
Specifies the status of the VPC endpoint service.
-- creating: indicates the VPC endpoint service is being created.
- available: indicates the VPC endpoint service is connectable.
- failed: indicates the creation of the VPC endpoint service failed.
+- creating: The VPC endpoint service is being created.
- available: The VPC endpoint service is connectable.
- failed: The VPC endpoint service failed to be created.
|
created_at
@@ -367,16 +351,7 @@
|
String
|
-Specifies the project ID. For details about how to obtain the project ID, see Obtaining a Project ID.
- |
-
-cidr_type
- |
-String
- |
-Specifies the network segment type. The type can be public or internal.
-- public: indicates the public subnet CIDR block.
- internal: indicates the private subnet CIDR block.
-The default value is internal.
+ | Specifies the project ID. For details about how to obtain the project ID, see Obtaining a Project ID.
|
ports
@@ -384,7 +359,7 @@
| Array of objects
|
Lists the port mappings opened to the VPC endpoint service. For details, see Table 6.
-Duplicate port mappings are not allowed in the same VPC endpoint service. If multiple VPC endpoint services share the same port_id value, service ports and terminal ports of all these endpoint services cannot be duplicated when the protocol is the same.
+Duplicate port mappings are not allowed in the same VPC endpoint service. If multiple VPC endpoint services share the same port_id value, either server_port or protocol, or both server_port and protocol of each of these endpoint services must be unique.
|
tcp_proxy
@@ -397,7 +372,7 @@
- Proxy Protocol: The client information is inserted into field tcp payload and transmitted to the server.
This parameter is available only when the server can parse fields tcp option and tcp payload.
The values are as follows:
-- close: indicates that the TOA and Proxy Protocol methods are neither used.
- toa_open: indicates that the TOA method is used.
- proxy_open: indicates that the Proxy Protocol method is used.
- open: indicates that the TOA and Proxy Protocol methods are both used.
+- close: The TOA and Proxy Protocol methods are neither used.
- toa_open: The TOA method is used.
- proxy_open: The Proxy Protocol method is used.
- open: The TOA and Proxy Protocol methods are both used.
- proxy_vni: The TOA Protocol method is not used. Proxy and virtual network ID are used.
The default value is close.
|
@@ -411,44 +386,44 @@
-
- Table 6 Port mapping parametersParameter
+
+Table 6 Port parametersParameter
|
-Type
+ | Type
|
-Description
+ | Description
|
-client_port
+ | client_port
|
-Integer
+ | Integer
|
-Specifies the port for accessing the VPC endpoint.
+ | Specifies the port for accessing the VPC endpoint.
This port is provided by the VPC endpoint, allowing you to access the VPC endpoint service. Supported range: 1 to 65535
|
-server_port
+ | server_port
|
-Integer
+ | Integer
|
-Specifies the port for accessing the VPC endpoint service.
+ | Specifies the port for accessing the VPC endpoint service.
This port is provided by the backend service to provide services. Supported range: 1 to 65535
|
-protocol
+ | protocol
|
-String
+ | String
|
-Specifies the protocol used in port mappings. The protocol can be TCPor UDP. The default protocol is TCP.
+ | Specifies the port mapping protocol. TCP is supported.
+The default value is TCP.
|
-
-Table 7 ResourceTags parametersParameter
+Table 7 Tags parametersParameter
|
Type
|
@@ -460,14 +435,14 @@
String
|
-Specifies the tag key. A tag key contains a maximum of 36 Unicode characters. This parameter cannot be left blank. It can contain only digits, letters, hyphens (-), and underscores (_).
+ | Specifies the tag key. A tag key contains a maximum of 36 Unicode characters. key cannot be left blank. It can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
|
value
|
String
|
-Specifies the tag value. A tag value contains a maximum of 43 Unicode characters and can be left blank. It can contain only digits, letters, hyphens (-), and underscores (_).
+ | Specifies the tag value. A tag value contains a maximum of 43 Unicode characters and can be left blank. It can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
|
@@ -486,7 +461,7 @@
"service_type":"interface",
"server_type":"VM",
"project_id":"6e9dfd51d1124e8d8498dce894923a0d",
- "created_at":"2018-01-30T07:42:01.174",
+ "created_at":"2018-01-30T07:42:01Z",
"ports":
[
{
@@ -502,7 +477,7 @@
]
}
-Status CodeFor details about status codes, see Status Code.
+
diff --git a/docs/vpcep/api-ref/vpcep_06_0202.html b/docs/vpcep/api-ref/vpcep_06_0202.html
index dfce1c9f4..f9169cbd3 100644
--- a/docs/vpcep/api-ref/vpcep_06_0202.html
+++ b/docs/vpcep/api-ref/vpcep_06_0202.html
@@ -1,11 +1,11 @@
- Querying Details of a VPC Endpoint Service
- FunctionThis API is used to query details of a VPC endpoint service.
+ Querying Details About a VPC Endpoint Service
+ FunctionThis API is used to query details about a VPC endpoint service.
URIGET /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}
- Table 1 describes the required parameters.
- Table 1 Parameter descriptionParameter
+Table 1 describes parameters in this URI.
+ Table 1 URI parametersParameter
|
Mandatory
|
@@ -17,7 +17,7 @@
Yes
|
-Specifies the project ID. For details about how to obtain the project ID, see Obtaining a Project ID.
+ | Specifies the project ID. For details about how to obtain the project ID, see Obtaining a Project ID.
|
vpc_endpoint_service_id
@@ -33,16 +33,16 @@
Request- Parameter description
None
- - Example request
This request is to query details of the VPC endpoint service whose ID is 4189d3c2-8882-4871-a3c2-d380272eed88. GET https://{endpoint}/v1/{project_id}/vpc-endpoint-services/4189d3c2-8882-4871-a3c2-d380272eed88
+ - Example request
This request is to query details about the VPC endpoint service whose ID is 4189d3c2-8882-4871-a3c2-d380272eed88. GET https://{endpoint}/v1/{project_id}/vpc-endpoint-services/4189d3c2-8882-4871-a3c2-d380272eed88
Response- Parameter description
-
Table 2 Response parametersParameter
+Table 2 Response parametersParameter
|
Type
|
-Description
+ | Description
|
@@ -57,8 +57,8 @@
String
|
-Specifies the ID for identifying the backend resource of the VPC endpoint service. The ID is in the form of the UUID. The values are as follows:
-- If the backend resource is an enhanced load balancer, the value is the ID of the port bound to the private IP address of the load balancer.
- If the backend resource is an ECS, the value is the NIC ID of the ECS where the VPC endpoint service is deployed.
- If the backend resource is a virtual IP address, the value is the NIC ID of the physical server where virtual resources are created.
+ | Specifies the ID for identifying the backend resource of the VPC endpoint service. The ID is in UUID format. The values are as follows:
+- If the backend resource is a load balancer, the value is the ID of the port bound to the private IP address of the load balancer.
- If the backend resource is an ECS, the value is the NIC ID of the ECS where the VPC endpoint service is deployed.
- If the backend resource is a virtual IP address, the value is the port ID of the physical server where virtual resources are created. (This value will be discarded. The LB type is recommended.)
- If the backend resource is a BMS, the value is the NIC ID of the BMS where the VPC endpoint service is deployed. (This value will be discarded. The LB type is recommended.)
|
pool_id
@@ -68,14 +68,6 @@
| Specifies the ID of the cluster associated with the target VPCEP resource.
|
-vip_port_id
- |
-String
- |
-Specifies the ID of the virtual NIC to which the virtual IP address is bound.
-This parameter is returned only when port_id is set to VIP.
- |
-
service_name
|
String
@@ -88,7 +80,7 @@
| String
|
Specifies the resource type.
-- VM: indicates the ECS.
- VIP: indicates the virtual IP address.
- LB: indicates the enhanced load balancer.
+- LB: indicates a load balancer.
- VM: indicates an ECS.
- VIP: indicates a virtual IP address. (This value has been discarded. The LB type is recommended.)
- BMS: indicates a BMS. (This value has been discarded. The LB type is recommended.)
|
vpc_id
@@ -103,7 +95,7 @@
| Boolean
|
Specifies whether connection approval is required.
-- false: indicates that connection approval is not required. The created VPC endpoint is in the Accepted state.
- true: indicates that connection approval is required. The created VPC endpoint is in the Pending acceptance state until the owner of the associated VPC endpoint service approves the connection.
+- false: Connection approval is not required. The created VPC endpoint is in the accepted state.
- true: Connection approval is required. The created VPC endpoint is in the pendingAcceptance state until the owner of the associated VPC endpoint service approves the connection.
|
status
@@ -111,7 +103,7 @@
| String
|
Specifies the status of the VPC endpoint service.
-- creating: indicates the VPC endpoint service is being created.
- available: indicates the VPC endpoint service is connectable.
- failed: indicates the creation of the VPC endpoint service failed.
- deleting: indicates the VPC endpoint service is being deleted.
+- creating: The VPC endpoint service is being created.
- available: The VPC endpoint service is connectable.
- failed: The VPC endpoint service failed to be created.
- deleting: The VPC endpoint service is being deleted.
|
service_type
@@ -144,16 +136,7 @@
|
String
|
-Specifies the project ID. For details about how to obtain the project ID, see Obtaining a Project ID.
- |
-
-cidr_type
- |
-String
- |
-Specifies the network segment type. The type can be public or internal.
-- public: indicates the public subnet CIDR block.
- internal: indicates the private subnet CIDR block.
-The default value is internal.
+ | Specifies the project ID. For details about how to obtain the project ID, see Obtaining a Project ID.
|
ports
@@ -161,7 +144,7 @@
| Array of objects
|
Lists the port mappings opened to the VPC endpoint service. For details, see Table 3.
-Duplicate port mappings are not allowed in the same VPC endpoint service. If multiple VPC endpoint services share the same port_id value, service ports and terminal ports of all these endpoint services cannot be duplicated when the protocol is the same.
+Duplicate port mappings are not allowed in the same VPC endpoint service. If multiple VPC endpoint services share the same port_id value, either server_port or protocol, or both server_port and protocol of each of these endpoint services must be unique.
|
tcp_proxy
@@ -174,7 +157,7 @@
- Proxy Protocol: The client information is inserted into field tcp payload and transmitted to the server.
This parameter is available only when the server can parse fields tcp option and tcp payload.
The values are as follows:
-- close: indicates that the TOA and Proxy Protocol methods are neither used.
- toa_open: indicates that the TOA method is used.
- proxy_open: indicates that the Proxy Protocol method is used.
- open: indicates that the TOA and Proxy Protocol methods are both used.
+- close: The TOA and Proxy Protocol methods are neither used.
- toa_open: The TOA method is used.
- proxy_open: The Proxy Protocol method is used.
- open: The TOA and Proxy Protocol methods are both used.
- proxy_vni: The TOA Protocol method is not used. Proxy and virtual network ID are used.
The default value is close.
|
@@ -193,15 +176,22 @@
This field is returned when the status of the VPC endpoint service changes to failed. For details, see Table 5.
+description
+ |
+String
+ |
+Supplementary information about the VPC endpoint service.
+ |
+
-Table 3 Port mapping parametersParameter
+Table 3 Port parametersParameter
|
Type
|
-Description
+ | Description
|
@@ -225,14 +215,15 @@
String
|
-Specifies the protocol used in port mappings. The protocol can be TCPor UDP. The default protocol is TCP.
+ | Specifies the port mapping protocol. TCP is supported.
+The default value is TCP.
|
-Table 4 ResourceTags parametersParameter
+Table 4 Tags parametersParameter
|
Type
|
@@ -244,14 +235,14 @@
String
|
-Specifies the tag key. A tag key contains a maximum of 36 Unicode characters. This parameter cannot be left blank. It can contain only digits, letters, hyphens (-), and underscores (_).
+ | Specifies the tag key. A tag key contains a maximum of 36 Unicode characters. key cannot be left blank. It can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
|
value
|
String
|
-Specifies the tag value. A tag value contains a maximum of 43 Unicode characters and can be left blank. It can contain only digits, letters, hyphens (-), and underscores (_).
+ | Specifies the tag value. A tag value contains a maximum of 43 Unicode characters and can be left blank. It can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
|
@@ -260,7 +251,7 @@
Table 5 Error parametersParameter
|
-Type
+ | Type
|
Description
|
@@ -296,7 +287,7 @@
"service_type":"interface",
"server_type":"VM",
"project_id":"6e9dfd51d1124e8d8498dce894923a0d",
- "created_at":"2018-01-30T07:42:01.174",
+ "created_at":"2018-01-30T07:42:01Z",
"ports":
[
{
@@ -312,7 +303,7 @@
]
}
-Status CodeFor details about status codes, see Status Code.
+
diff --git a/docs/vpcep/api-ref/vpcep_06_0203.html b/docs/vpcep/api-ref/vpcep_06_0203.html
index a9076eae9..5f854e57c 100644
--- a/docs/vpcep/api-ref/vpcep_06_0203.html
+++ b/docs/vpcep/api-ref/vpcep_06_0203.html
@@ -1,11 +1,11 @@
Modifying a VPC Endpoint Service
- FunctionThis API is used to modify a VPC endpoint service.
+ FunctionThis API is used to modify a VPC endpoint service.
URIPUT /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}
- Table 1 describes the required parameters.
- Table 1 Parameter descriptionParameter
+Table 1 describes parameters in this URI.
+ Table 1 URI parametersParameter
|
Mandatory
|
@@ -17,7 +17,7 @@
Yes
|
-Specifies the project ID. For details about how to obtain the project ID, see Obtaining a Project ID.
+ | Specifies the project ID. For details about how to obtain the project ID, see Obtaining a Project ID.
|
vpc_endpoint_service_id
@@ -33,13 +33,13 @@
Request- Parameter description
-
Table 2 Request parametersParameter
+Table 2 Request parametersParameter
|
-Mandatory
+ | Mandatory
|
Type
|
-Description
+ | Description
|
@@ -50,7 +50,7 @@
Boolean
|
Specifies whether connection approval is required.
-- false: indicates that connection approval is not required. The created VPC endpoint is in the Accepted state.
- true: indicates that connection approval is required. The created VPC endpoint is unavailable until the owner of the associated VPC endpoint service approves the connection.
+- false: Connection approval is not required. The created VPC endpoint is in the accepted state.
- true: Connection approval is required. The created VPC endpoint is unavailable until the owner of the associated VPC endpoint service approves the connection.
The default value is true.
|
@@ -70,7 +70,7 @@
Array of objects
|
Lists the port mappings opened to the VPC endpoint service. For details, see Table 3.
-Duplicate port mappings are not allowed in the same VPC endpoint service. If multiple VPC endpoint services share the same port_id value, service ports and terminal ports of all these endpoint services cannot be duplicated when the protocol is the same. A maximum of 200 port mappings can be created at a time.
+Duplicate port mappings are not allowed in the same VPC endpoint service. If multiple VPC endpoint services share the same port_id value, either server_port or protocol, or both server_port and protocol of each of these endpoint services must be unique. A maximum of 200 port mappings can be created at a time.
|
port_id
@@ -79,30 +79,46 @@
|
String
|
-Specifies the ID for identifying the backend resource of the VPC endpoint service. The ID is in the form of the UUID. The values are as follows:
-- If the backend resource is an enhanced load balancer, the value is the ID of the port bound to the private IP address of the load balancer. For details, see response field vip_port_id in Querying Details of a Load Balancer in the Elastic Load Balancing API Reference.
- If the backend resource is an ECS, the value is the NIC ID of the ECS where the VPC endpoint service is deployed. For details, see Querying NICs of an ECS in the Elastic Load Balancing API Reference.
- If the backend resource is a virtual IP address, the value is the NIC ID of the physical server where virtual resources are created.
+ | Specifies the ID for identifying the backend resource of the VPC endpoint service. The ID is in UUID format. The values are as follows:
+- If the backend resource is a load balancer, the value is the ID of the port bound to the private IP address of the load balancer. For details, see response field port_id in Querying Details of a Load Balancer and Viewing Details of a Load Balancer in the Elastic Load Balancing API Reference.
- If the backend resource is an ECS, the value is the NIC ID of the ECS where the VPC endpoint service is deployed. For details, see port_id in the response in section Querying NICs of an ECS in the Elastic Cloud Server API Reference.
- If the backend resource is a virtual IP address, the value is the port ID of the physical server where virtual resources are created. (This value will be discarded. The LB type is recommended.)
- If the backend resource is a BMS, the value is the NIC ID of the BMS where the VPC endpoint service is deployed. (This value will be discarded. The LB type is recommended.)
|
-vip_port_id
+ | tcp_proxy
|
-No
+ | No
|
-String
+ | String
|
-Specifies the ID of the virtual NIC to which the virtual IP address is bound.
+ | Specifies whether the client IP address and port number or marker_id information is transmitted to the server. The following methods are supported:
+- TCP TOA: The client information is inserted into field tcp option and transmitted to the server.
NOTE: TCP TOA is supported only when the backend resource is OBS.
+
+ - Proxy Protocol: The client information is inserted into field tcp payload and transmitted to the server.
+This parameter is available only when the server can parse fields tcp option and tcp payload.
+The values are as follows:
+- close: The TOA and Proxy Protocol methods are neither used.
- toa_open: The TOA method is used.
- proxy_open: The Proxy Protocol method is used.
- open: The TOA and Proxy Protocol methods are both used.
- proxy_vni: The TOA Protocol method is not used. Proxy and virtual network ID are used.
+The default value is close.
+ |
+
+description
+ |
+No
+ |
+String
+ |
+Supplementary information about the VPC endpoint service. The description can contain a maximum of 128 characters and cannot contain left angle brackets (<) or right angle brackets (>).
|
-Table 3 Port mapping parametersParameter
+Table 3 Port parametersParameter
|
Mandatory
|
-Type
+ | Type
|
-Description
+ | Description
|
@@ -132,7 +148,8 @@
String
|
-Specifies the protocol used in port mappings. The protocol can be TCP or UDP. The default protocol is TCP.
+ | Specifies the port mapping protocol. TCP is supported.
+The default value is TCP.
|
@@ -160,11 +177,11 @@
Response- Parameter description
-
Table 4 Response parametersParameter
+Table 4 Response parametersParameter
|
-Type
+ | Type
|
-Description
+ | Description
|
@@ -179,8 +196,8 @@
String
|
-Specifies the ID for identifying the backend resource of the VPC endpoint service. The ID is in the form of the UUID. The values are as follows:
-- If the backend resource is an enhanced load balancer, the value is the ID of the port bound to the private IP address of the load balancer.
- If the backend resource is an ECS, the value is the NIC ID of the ECS where the VPC endpoint service is deployed.
- If the backend resource is a virtual IP address, the value is the NIC ID of the physical server where virtual resources are created.
+ | Specifies the ID for identifying the backend resource of the VPC endpoint service. The ID is in UUID format. The values are as follows:
+- If the backend resource is a load balancer, the value is the ID of the port bound to the private IP address of the load balancer.
- If the backend resource is an ECS, the value is the NIC ID of the ECS where the VPC endpoint service is deployed.
- If the backend resource is a virtual IP address, the value is the port ID of the physical server where virtual resources are created. (This value will be discarded. The LB type is recommended.)
- If the backend resource is a BMS, the value is the NIC ID of the BMS where the VPC endpoint service is deployed. (This value will be discarded. The LB type is recommended.)
|
pool_id
@@ -190,13 +207,6 @@
| Specifies the ID of the cluster associated with the target VPCEP resource.
|
-vip_port_id
- |
-String
- |
-Specifies the ID of the virtual NIC to which the virtual IP address is bound.
- |
-
service_name
|
String
@@ -209,7 +219,7 @@
| String
|
Specifies the resource type.
-- VM: indicates the ECS.
- VIP: indicates the virtual IP address.
- LB: indicates the enhanced load balancer.
+- LB: indicates a load balancer.
- VM: indicates an ECS.
- VIP: indicates a virtual IP address. (This value has been discarded. The LB type is recommended.)
- BMS: indicates a BMS. (This value has been discarded. The LB type is recommended.)
|
vpc_id
@@ -224,7 +234,7 @@
| Boolean
|
Specifies whether connection approval is required.
-- false: indicates that connection approval is not required. The created VPC endpoint is in the Accepted state.
- true: indicates that connection approval is required. The created VPC endpoint is in the Pending acceptance state until the owner of the associated VPC endpoint service approves the connection.
+- false: Connection approval is not required. The created VPC endpoint is in the accepted state.
- true: Connection approval is required. The created VPC endpoint is in the pendingAcceptance state until the owner of the associated VPC endpoint service approves the connection.
|
status
@@ -232,7 +242,7 @@
| String
|
Specifies the status of the VPC endpoint service.
-available: indicates the VPC endpoint service is connectable.
+- creating: The VPC endpoint service is being created.
- available: The VPC endpoint service is connectable.
- failed: The VPC endpoint service failed to be created.
|
service_type
@@ -265,16 +275,7 @@
|
String
|
-Specifies the project ID. For details about how to obtain the project ID, see Obtaining a Project ID.
- |
-
-cidr_type
- |
-String
- |
-Specifies the network segment type. The type can be public or internal.
-- public: indicates the public subnet CIDR block.
- internal: indicates the private subnet CIDR block.
-The default value is internal.
+ | Specifies the project ID. For details about how to obtain the project ID, see Obtaining a Project ID.
|
ports
@@ -282,21 +283,21 @@
| Array of objects
|
Lists the port mappings opened to the VPC endpoint service. For details, see Table 5.
-Duplicate port mappings are not allowed in the same VPC endpoint service. If multiple VPC endpoint services share the same port_id value, service ports and terminal ports of all these endpoint services cannot be duplicated when the protocol is the same.
+Duplicate port mappings are not allowed in the same VPC endpoint service. If multiple VPC endpoint services share the same port_id value, either server_port or protocol, or both server_port and protocol of each of these endpoint services must be unique.
|
tcp_proxy
|
String
|
-Specifies whether the client IP address and port number or marker_id information is transmitted to the server. The following methods are supported:
-- TCP TOA: The client information is inserted into field tcp option and transmitted to the server.
NOTE: TCP TOA is supported only when the backend resource is OBS.
+ Specifies whether the client IP address and port number or marker_id information is transmitted to the server. The following methods are supported:
+- TCP TOA: The client information is inserted into field tcp option and transmitted to the server.
NOTE: TCP TOA is supported only when the backend resource is OBS.
- - Proxy Protocol: The client information is inserted into field tcp payload and transmitted to the server.
-This parameter is available only when the server can parse fields tcp option and tcp payload.
+- Proxy Protocol: The client information is inserted into field tcp payload and transmitted to the server.
+This parameter is available only when the server can parse fields tcp option and tcp payload.
The values are as follows:
-- close: indicates that the TOA and Proxy Protocol methods are neither used.
- toa_open: indicates that the TOA method is used.
- proxy_open: indicates that the Proxy Protocol method is used.
- open: indicates that the TOA and Proxy Protocol methods are both used.
-The default value is close.
+- close: The TOA and Proxy Protocol methods are neither used.
- toa_open: The TOA method is used.
- proxy_open: The Proxy Protocol method is used.
- open: The TOA and Proxy Protocol methods are both used.
- proxy_vni: The TOA Protocol method is not used. Proxy and virtual network ID are used.
+The default value is close.
|
|
tags
@@ -306,15 +307,22 @@
| Lists the resource tags. For details, see Table 6.
|
+description
+ |
+String
+ |
+Supplementary information about the VPC endpoint service.
+ |
+
- Table 5 Port mapping parametersParameter
+Table 5 Port parametersParameter
|
Type
|
-Description
+ | Description
|
@@ -338,7 +346,8 @@
String
|
-Specifies the protocol used in port mappings. The protocol can be TCPor UDP. The default protocol is TCP.
+ | Specifies the port mapping protocol. TCP is supported.
+The default value is TCP.
|
@@ -346,7 +355,7 @@
-Table 6 ResourceTags parametersParameter
+Table 6 Tags parametersParameter
|
Type
|
@@ -358,14 +367,14 @@
String
|
-Specifies the tag key. A tag key contains a maximum of 36 Unicode characters. This parameter cannot be left blank. It can contain only digits, letters, hyphens (-), and underscores (_).
+ | Specifies the tag key. A tag key contains a maximum of 36 Unicode characters. key cannot be left blank. It can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
|
value
|
String
|
-Specifies the tag value. A tag value contains a maximum of 43 Unicode characters and can be left blank. It can contain only digits, letters, hyphens (-), and underscores (_).
+ | Specifies the tag value. A tag value contains a maximum of 43 Unicode characters and can be left blank. It can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
|
@@ -384,7 +393,7 @@
"service_type":"interface",
"server_type":"VM",
"project_id":"6e9dfd51d1124e8d8498dce894923a0d",
- "created_at":"2018-01-30T07:42:01.174",
+ "created_at":"2018-01-30T07:42:01Z",
"ports":
[
{
@@ -400,7 +409,7 @@
]
}
-Status CodeFor details about status codes, see Status Code.
+
diff --git a/docs/vpcep/api-ref/vpcep_06_0204.html b/docs/vpcep/api-ref/vpcep_06_0204.html
index 4cbe0bc8f..1c0ed261b 100644
--- a/docs/vpcep/api-ref/vpcep_06_0204.html
+++ b/docs/vpcep/api-ref/vpcep_06_0204.html
@@ -1,11 +1,13 @@
Deleting a VPC Endpoint Service
- FunctionThis API is used to delete a VPC endpoint service.
+ FunctionThis API is used to delete a VPC endpoint service.
+ This API is asynchronous. If it is successfully invoked, status code 200 is returned, indicating that the request has been successfully delivered. It takes 1 to 2 minutes to delete a VPC endpoint service. You can view the deletion result by performing operations in Querying Details About a VPC Endpoint Service.
+
URIDELETE /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}
- Table 1 describes the required parameters.
- Table 1 ParametersParameter
+Table 1 describes parameters in this URI.
+ Table 1 URI parametersParameter
|
Mandatory
|
@@ -17,7 +19,7 @@
Yes
|
-Specifies the project ID. For details about how to obtain the project ID, see Obtaining a Project ID.
+ | Specifies the project ID. For details about how to obtain the project ID, see Obtaining a Project ID.
|
vpc_endpoint_service_id
@@ -39,7 +41,7 @@
-Status CodeFor details about status codes, see Status Code.
+
diff --git a/docs/vpcep/api-ref/vpcep_06_0205.html b/docs/vpcep/api-ref/vpcep_06_0205.html
index 797c8fd90..1fd17e63c 100644
--- a/docs/vpcep/api-ref/vpcep_06_0205.html
+++ b/docs/vpcep/api-ref/vpcep_06_0205.html
@@ -4,8 +4,8 @@
FunctionThis API is used to query VPC endpoint services.
URIGET /v1/{project_id}/vpc-endpoint-services?endpoint_service_name={endpoint_service_name}&id={id}&sort_key={sort_key}&sort_dir={sort_dir}&limit={limit}&offset={offset}&status={status}
- Table 1 describes the required parameters.
- Table 1 Parameter descriptionParameter
+Table 1 describes the parameter in this URI.
+ Table 1 URI parameterParameter
|
Mandatory
|
@@ -17,107 +17,108 @@
Yes
|
-Specifies the project ID. For details about how to obtain the project ID, see Obtaining a Project ID.
+ | Specifies the project ID. For details about how to obtain the project ID, see Obtaining a Project ID.
|
-
-Request- Parameter description
-
Table 2 Request parametersParameter
+
+Table 2 Query parametersParameter
|
-Mandatory
+ | Mandatory
|
-Type
+ | Type
|
-Description
+ | Description
|
-endpoint_service_name
+ | endpoint_service_name
|
-No
+ | No
|
-String
+ | String
|
-Specifies the name of the VPC endpoint service. The name is not case-sensitive and supports fuzzy match.
+ | Specifies the name of the VPC endpoint service. The name is not case-sensitive and supports fuzzy match.
|
-id
+ | id
|
-No
+ | No
|
-String
+ | String
|
-Specifies the unique ID of the VPC endpoint service.
+ | Specifies the unique ID of the VPC endpoint service.
|
-status
+ | status
|
-No
+ | No
|
-String
+ | String
|
-Specifies the status of the VPC endpoint service.
-- creating: indicates the VPC endpoint service is being created.
- available: indicates the VPC endpoint service is connectable.
- failed: indicates the creation of the VPC endpoint service failed.
- deleting: indicates the VPC endpoint service is being deleted.
+ | Specifies the status of the VPC endpoint service.
+- creating: The VPC endpoint service is being created.
- available: The VPC endpoint service is connectable.
- failed: The VPC endpoint service failed to be created.
- deleting: The VPC endpoint service is being deleted.
|
-sort_key
+ | sort_key
|
-No
+ | No
|
-String
+ | String
|
-Specifies the sorting field of the VPC endpoint service list. The field can be:
-- create_at: indicates that VPC endpoint services are sorted by creation time.
- update_at: indicates that VPC endpoint services are sorted by update time.
-The default field is create_at.
+ | Specifies the sorting field of the VPC endpoint service list. The field can be:
+- created_at: VPC endpoint services are sorted by creation time.
- updated_at: VPC endpoint services are sorted by update time.
+The default field is created_at.
|
-sort_dir
+ | sort_dir
|
-No
+ | No
|
-String
+ | String
|
-Specifies the sorting method of the VPC endpoint service list. The method can be:
-- desc: indicates that VPC endpoint services are sorted in the descending order.
- asc: indicates that VPC endpoint services are sorted in the ascending order.
+ | Specifies the sorting method of the VPC endpoint service list. The method can be:
+- desc: VPC endpoint services are sorted in descending order.
- asc: VPC endpoint services are sorted in ascending order.
The default method is desc.
|
-limit
+ | limit
|
-No
+ | No
|
-Integer
+ | Integer
|
-Specifies the maximum number of VPC endpoint services displayed on each page.
+ | Specifies the maximum number of VPC endpoint services displayed on each page.
The number ranges from 0 to 1000 and is generally 10, 20, or 50. The default number is 10.
|
-offset
+ | offset
|
-No
+ | No
|
-Integer
+ | Integer
|
-Specifies the offset.
+ | Specifies the offset.
All VPC endpoint services after this offset will be queried. The offset must be an integer greater than 0 but less than the number of VPC endpoint services.
|
+
+
Response- Parameter description
-
Table 3 Response parametersParameter
+Table 3 Response parameters |
|---|
|
|---|
|
|---|
|
|---|
| |
|---|
|
|---|
|
|---|
|
|---|
|
|---|
|
|---|
| |
|---|
|---|
|
|---|
|
|---|
|
|---|
| |
|---|
|
|---|
|
|---|
|
|---|
| |
|---|
|
|---|
|
|---|
|
|---|
|---|
|
|---|
|
|---|
|
|---|
|---|
|
|---|