Modifying a Microservice Schema
Function
Modify a microservice schema based on schema_id.
Restrictions
In versions earlier than 2.3.33, schema overwriting is not supported in production environment. In version 2.3.33 and later, the environment variable SCHEMA_EDITABLE can be used to support schema overwriting.
Authorization Information
Each account has all of the permissions required to call all APIs, but IAM users must have the required permissions specifically assigned.
- If you are using role/policy-based authorization, see the required permissions in Permissions and Supported Actions.
- If you are using identity policy-based authorization, no identity policy-based permissions are required for calling this API.
URI
PUT /v4/{project_id}/registry/microservices/{service_id}/schemas/{schema_id}
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
project_id |
Yes |
String |
Fixed value: default. |
|
service_id |
Yes |
String |
Microservice ID, which must be unique. The value contains 1 to 64 characters. Regular expression: ^.*$. For details about how to obtain the service ID list, see Querying Information About All Microservices. |
|
schema_id |
Yes |
String |
Microservice schema ID, which must be unique. The value contains 1 to 160 characters. Regular expression: ^[a-zA-Z0-9]{1,160}$|^[a-zA-Z0-9][a-zA-Z0-9_-.]{0,158}[a-zA-Z0-9]$. For details about how to obtain the schema ID list, see Querying All Schema Information About a Microservice. |
Request
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
Authorization |
No |
String |
This parameter is mandatory if security authentication is enabled for an exclusive ServiceComb engine. Otherwise, this parameter is not required. The token of an exclusive ServiceComb engine with security authentication enabled is in the following format: Authorization:Bearer {Token}
For details about how to obtain the token, see Obtaining the User Token of an Exclusive ServiceComb Engine. |
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
schema |
Yes |
String |
Schema content. |
|
summary |
No |
String |
Schema summary. |
Response
Status code: 400
|
Parameter |
Type |
Description |
|---|---|---|
|
errorCode |
String |
Error code. |
|
errorMessage |
String |
Error message. |
|
detail |
String |
Location details. |
Status code: 500
|
Parameter |
Type |
Description |
|---|---|---|
|
errorCode |
String |
Error code. |
|
errorMessage |
String |
Error message. |
|
detail |
String |
Location details. |
Example Request
Modify the content and summary of a schema with specified service_id and schema_id.
PUT https://{endpoint}/v4/{project_id}/registry/microservices/{service_id}/schemas/{schema_id}
{
"schema": "---\nswagger: \"2.0\"\ninfo:\n version: \"1.0.0\"\n title: \"swagger definition for com.service.provider.controller.ProviderImpl\"\n x-java-interface: \"cse.gen.springmvc.provider.provider.ProviderImplIntf\"\nbasePath: \"/provider\"\nconsumes:\n- \"application/json\"\nproduces:\n- \"application/json\"\npaths:\n /helloworld:\n get:\n operationId: \"helloworld\"\n produces:\n - \"application/json\"\n parameters:\n - name: \"name\"\n in: \"query\"\n required: true\n type: \"string\"\n responses:\n 200:\n description: \"response of 200\"\n schema:\n type: \"string\"\n",
"summary": "test"
}
Example Response
None
Status Code
|
Status Code |
Description |
|---|---|
|
200 |
OK |
|
400 |
Bad Request |
|
500 |
Internal Server Error |
Error Code
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot