RemoveTraficMatchRuleFromTrafficMarkingPolicy - Cloud Enterprise Network

This API is deprecated. You are advised to use Cbn(2017-09-12) - RemoveTrafficMatchRuleFromTrafficMarkingPolicy.

Removes a traffic classification rule from a traffic marking policy.

Operation description

Precautions

The RemoveTraficMatchRuleFromTrafficMarkingPolicy operation is deprecated and will be discontinued soon. To delete a traffic classification rule, call the RemoveTrafficMatchRuleFromTrafficMarkingPolicy operation. Maintenance on this document has stopped.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Debug

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

Operation: the value that you can use in the Action element to specify the operation on a resource.
Access level: the access level of each operation. The levels are read, write, and list.
Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
Condition Key: the condition key that is defined by the cloud service.
Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.

Operation	Access level	Resource type	Condition key	Associated operation
cen:RemoveTraficMatchRuleFromTrafficMarkingPolicy	delete	All Resources *	none	none

Request parameters

Parameter	Type	Required	Description	Example
ClientToken	string	No	The client token that is used to ensure the idempotence of the request. You can use the client to generate the token, but you must make sure that the token is unique among different requests. The token can contain only ASCII characters. Note If you do not specify this parameter, the system automatically uses the request ID as the client token. The request ID may be different for each request.	123e4567-e89b-12d3-a456-426****
DryRun	boolean	No	Specifies whether to perform only a dry run, without performing the actual request. Valid values: true: performs only a dry run. The system checks the request for potential issues, including missing parameter values, incorrect request syntax, and service limits. If the request fails the dry run, an error code is returned. If the request passes the dry run, the `DryRunOperation` error code is returned. false (default): performs a dry run and performs the actual request.	false
TrafficMarkingPolicyId	string	Yes	The ID of the traffic marking policy.	tm-d33hdczo3qo8ta****
TrafficMarkRuleIds	array	No	The ID of the traffic classification rule.
	string	No	The ID of the traffic classification rule. You can delete at most 20 traffic classification rules in each call. You can call the ListTrafficMarkingPolicies operation to query IDs of traffic classification rules.	tm-rule-15jtgapsat62r9****

Response parameters

Parameter	Type	Description	Example
	object	The response parameters.
RequestId	string	The request ID.	6DF9A765-BCD2-5C7E-8C32-C35C8A361A39

Examples

Sample success responses

JSONformat

{
  "RequestId": "6DF9A765-BCD2-5C7E-8C32-C35C8A361A39"
}

Error codes

HTTP status code	Error code	Error message	Description
400	IncorrectStatus.TrafficMarkingPolicy	TrafficMarkingPolicy status is invalid.	The error message returned because the status of the traffic marking policy does not support this operation. Try again later.
400	InvalidTrafficMarkingPolicyId.NotFound	The specified TrafficMarkingPolicyId is not found.	The error message returned because the specified traffic marking policy ID (TrafficMarkingPolicyId) does not exist.
400	IllegalParam.TrafficMarkingRuleIds	The specified TrafficMarkingRuleIds is invalid.	The error message returned because the TrafficMarkingRuleIds parameter is set to an invalid value.
400	InvalidParameter	Invalid parameter.	The error message returned because the parameter is set to an invalid value.
400	Unauthorized	The AccessKeyId is unauthorized.	The error message returned because you do not have the permissions to perform this operation.

For a list of error codes, visit the Service error codes.

Change history

Change time	Summary of changes	Operation
2022-12-22	The Error code has changed	View Change Details
2022-09-19	The API operation is deprecated. The Error code has changed	View Change Details
2021-11-26	Add Operation	View Change Details