Deleting a SQL Interception Rule
Function
This API is used to delete a SQL interception rule.
Authorization
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 the required permissions in Introduction.
- 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
Dependency
dli:sqldefendrule:delete
Write
-
-
-
-
URI
DELETE /v1/{project_id}/sql-defend-rules/{rule_id}
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
project_id |
Yes |
String |
Project ID, which is used for resource isolation. For how to obtain a project ID, see Obtaining a Project ID. |
|
rule_id |
Yes |
String |
Unique ID of an interception rule. |
Request Parameters
None
Response Parameters
|
Parameter |
Type |
Description |
|---|---|---|
|
is_success |
Boolean |
Whether the request is successfully executed. true indicates that the request is successfully executed. |
|
message |
String |
System prompt. If the execution succeeds, this parameter may be left blank. |
Example Request
None
Example Response
None
Status Codes
|
Status Code |
Description |
|---|---|
|
201 |
The rule is successfully deleted. |
|
400 |
Request error. |
|
500 |
Internal server error. |
Error Codes
If an error occurs when this API is called, the system does not return the result similar to the preceding example, but returns an error code and error message. For details, 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