检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
Deleting a configuration item Single deletion Click More > Delete in the Operation column of the target configuration item. In the displayed dialog box, click OK. Batch deletion Select the configuration items to be deleted. Click Delete Configuration Item.
In this case, you need to delete the components, create them again, and then deploy them. ServiceStage release management can be used to migrate and upgrade components across AZs. Batch clone release tasks can be used to migrate components across AZs.
The Configuration Management page allows you to create, edit, and delete configurations. Created configurations are displayed in a list.
To delete microservices in batches, select the microservices to be deleted and click Delete above the microservices. To delete one microservice, locate the row that contains the microservice to be deleted and click Delete in the Operation column.
Click Environment Variables to delete a custom environment variable. Single deletion: Click Delete in the Operation column of the target custom environment variable. Batch deletion: Select the target custom environment variables and click Bulk Delete. Click OK.
Delete a bound CSS Elasticsearch instance: Click . Parent topic: Managing Cloud Service Settings of a Component
Unbinding a configuration file will not delete it. To delete it, see Deleting a Configuration File. Binding a Configuration File Choose Application Settings > Add Configuration File. Set the configuration file parameters by referring to the following table.
Delete a bound GaussDB instance: Click . Parent topic: Managing Cloud Service Settings of a Component
Delete a bound DMS for RocketMQ: Click . Parent topic: Managing Cloud Service Settings of a Component
Delete the deployed microservice application component instances. Choose Application Management. Click the application where the microservice application is located. The Overview page is displayed.
Operation Description Restart a single instance If an instance of a container-deployed component is abnormal, you can delete the instance to restart it. Select the instance to be deleted and click Delete in the Operation column. In the displayed dialog box, click OK.
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 resource does not exist, a new resource will be created.
Unbinding a configuration file will not delete it. To delete it, see Deleting a Configuration File. Binding a Configuration File Choose Application Settings > Add Configuration File. Set the configuration file parameters by referring to the following table.
Figure 3 Microservice degraded Click to delete the service degradation policy to prevent it from affecting user experience. Figure 4 Deleting a policy Parent topic: Hosting and Managing a Weather Forecast Microservice Application on ServiceStage
Delete a bound distributed cache: Click . Parent topic: Managing Cloud Service Settings of a Component
For example, some software developers in your enterprise need to use ServiceStage resources but must not delete them or perform any high-risk operations.
In this case, you need to delete the components, create them again, and then deploy them. To upgrade component versions in batches, ServiceStage allows you to upgrade components in batches. However, only components in the same application can be upgraded in batches.
Delete a bound RDS instance: Click . Parent topic: Managing Cloud Service Settings of a Component
Stopping Billing To stop using ServiceStage, unsubscribe from or delete it to avoid further fees. For details, see Stopping Billing. Cost Management ServiceStage costs include costs of ownership and O&M.
If you no longer use application instances deployed on ServiceStage, stop or delete them to avoid further fees. Configure the Balance Alert function on the Billing Center > Overview page.
