Upgrading a Microservice Engine

This API is used to upgrade a microservice engine, including exclusive ServiceComb engine, application gateway, and registry/configuration center.

PUT /v2/{project_id}/enginemgr/engines/{engine_id}/upgrade

**Table 1** Path parameters
Parameter	Mandatory	Type	Description
project_id	Yes	String	Project ID.
engine_id	Yes	String	ID of the engine to be upgraded.

**Table 2** Request header parameters
Parameter	Mandatory	Type	Description
X-Auth-Token	Yes	String	User token.
X-Enterprise-Project-ID	No	String	If this parameter is not set, the default enterprise project is default and the ID is 0.
Content-Type	Yes	String	Set it to application/json;charset=UTF-8.
Accept	Yes	String	Set it to application/json.

**Table 3** Request body parameter
Parameter	Mandatory	Type	Description
version	Yes	String	Version number. Maximum length: 24

Status code: 200

**Table 4** Response body parameters
Parameter	Type	Description
id	String	Microservice engine ID.
name	String	Microservice engine name.
jobId	Integer	ID of the job executed by a microservice engine.

Status code: 400

Status code: 500

{
  "version" : "2.4.0"
}

Status code: 200

Response structure for upgrading a microservice engine.

{
  "id" : "891bf21a-4024-4f47-b38c-bd259ca8f10a",
  "name" : "test",
  "jobId" : 17655
}

Parent topic: Engine Management

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.