Modifying an Application Rule
Function
Modifies an application rule.
Debugging
You can debug this API through automatic authentication in API Explorer or use the SDK sample code generated by API Explorer.
Authorization Information
Each account has all the permissions required to call all APIs, but IAM users must be assigned the required permissions.
- If you are using role/policy-based authorization, see Permissions Policies and Supported Actions for details on the required permissions.
- If you are using identity policy-based authorization, the following identity policy-based permissions are required.
Action
Access Level
Resource Type (*: required)
Condition Key
Alias
Dependencies
workspace:appcenter:updateAppRule
Write
-
-
-
-
URI
PATCH /v1/{project_id}/app-center/app-rules/{rule_id}
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
project_id |
Yes |
String |
Project ID. |
|
rule_id |
Yes |
String |
Rule ID. |
Request Parameters
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
name |
No |
String |
Rule name: |
|
description |
No |
String |
Rule description: |
|
rule |
No |
Rule object |
Rule information. |
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
scope |
Yes |
String |
Application scope of a rule: PRODUCT: product PATH: path |
|
product_rule |
No |
ProductRule object |
Product rule information. The process name, product name, and publisher must match. If the value is empty or *, any match is allowed. Example: Publisher Name: * Product Name: Huawei Process Name: * A product whose name is Huawei is considered a match. |
|
path_rule |
No |
PathRule object |
Path rule information, which restricts the corresponding path and subpath. |
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
identify_condition |
No |
String |
Identification condition. |
|
publisher |
No |
String |
Publisher name: |
|
product_name |
No |
String |
Product name: |
|
process_name |
No |
String |
Process name: |
|
support_os |
No |
String |
OS type. This field exists only for built-in rules. |
|
version |
No |
String |
Version: |
|
product_version |
No |
String |
Product version: |
Response Parameters
Status code: 200
|
Parameter |
Type |
Description |
|---|---|---|
|
id |
String |
Rule ID. |
|
name |
String |
Rule name. |
|
description |
String |
Rule description. |
|
rule |
Rule object |
Rule information. |
|
rule_source |
String |
Rule source. |
|
create_time |
String |
Creation time. |
|
update_time |
String |
Update time. |
|
Parameter |
Type |
Description |
|---|---|---|
|
scope |
String |
Application scope of a rule: PRODUCT: product PATH: path |
|
product_rule |
ProductRule object |
Product rule information. The process name, product name, and publisher must match. If the value is empty or *, any match is allowed. Example: Publisher Name: * Product Name: Huawei Process Name: * A product whose name is Huawei is considered a match. |
|
path_rule |
PathRule object |
Path rule information, which restricts the corresponding path and subpath. |
|
Parameter |
Type |
Description |
|---|---|---|
|
identify_condition |
String |
Identification condition. |
|
publisher |
String |
Publisher name: |
|
product_name |
String |
Product name: |
|
process_name |
String |
Process name: |
|
support_os |
String |
OS type. This field exists only for built-in rules. |
|
version |
String |
Version: |
|
product_version |
String |
Product version: |
Status code: 400
|
Parameter |
Type |
Description |
|---|---|---|
|
error_code |
String |
Error code, which is returned upon failure. |
|
error_msg |
String |
Error description. |
Status code: 401
|
Parameter |
Type |
Description |
|---|---|---|
|
error_code |
String |
Error code, which is returned upon failure. |
|
error_msg |
String |
Error description. |
Status code: 403
|
Parameter |
Type |
Description |
|---|---|---|
|
error_code |
String |
Error code, which is returned upon failure. |
|
error_msg |
String |
Error description. |
Status code: 404
|
Parameter |
Type |
Description |
|---|---|---|
|
error_code |
String |
Error code, which is returned upon failure. |
|
error_msg |
String |
Error description. |
Status code: 405
|
Parameter |
Type |
Description |
|---|---|---|
|
error_code |
String |
Error code, which is returned upon failure. |
|
error_msg |
String |
Error description. |
Status code: 500
|
Parameter |
Type |
Description |
|---|---|---|
|
error_code |
String |
Error code, which is returned upon failure. |
|
error_msg |
String |
Error description. |
Status code: 503
|
Parameter |
Type |
Description |
|---|---|---|
|
error_code |
String |
Error code, which is returned upon failure. |
|
error_msg |
String |
Error description. |
Example Requests
{
"name" : "string",
"description" : "string",
"rule" : {
"scope" : "PRODUCT",
"product_rule" : {
"identify_condition" : "productName",
"publisher" : null,
"product_name" : "HUAWEI",
"process_name" : "Huawei.exe",
"support_os" : "Windows",
"version" : "1.0.0.1",
"product_version" : "1.0.0.1"
},
"path_rule" : {
"path" : "D:\\\\tmp"
}
}
}
Example Responses
Status code: 200
Response to a successful request.
{
"id" : "string",
"name" : "string",
"description" : "string",
"rule" : { },
"rule_source" : "string",
"create_time" : "2025-05-24T10:42:12.338Z",
"update_time" : "2025-05-24T10:42:12.338Z"
}
Status Codes
|
Status Code |
Description |
|---|---|
|
200 |
Response to a successful request. |
|
400 |
The request cannot be understood by the server due to malformed syntax. |
|
401 |
Authentication failed. |
|
403 |
No operation permissions. |
|
404 |
No resources found. |
|
405 |
The method specified in the request is not allowed. |
|
500 |
An internal service error occurred. For details about the error code, see the error code description. |
|
503 |
Service unavailable. |
Error Codes
See Error Codes.
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