Automate Container Scan Rules with API - Container Registry

Updates a scan rule.

Operation description

The whitelist of this API operation is available. Submit a ticket.

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:
- For mandatory resource types, indicate with a prefix of * .
- 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
cr:UpdateScanRule	update	*ScanRule `acs:cr:{#regionId}:{#accountId}:instance/{#instanceId}/scanrule/{#scanRuleId}`	none	none

Request parameters

Parameter	Type	Required	Description	Example
InstanceId	string	Yes	The instance ID.	cri-4abntrj42twd****
ScanRuleId	string	Yes	The rule ID.	crscnr-3qmkeiuggfpjkfrq
RuleName	string	Yes	The rule name.	scan-test
ScanScope	string	Yes	The scan scope. Valid values: NAMESPACE: namespace. REPO: repository. Enumeration Value: INSTANCE NAMESPACE REPO	REPO
TriggerType	string	Yes	The trigger type. Valid values: AUTO: automatically triggers. MANUAL: manually triggers.	AUTO
Namespaces	array	No	The list of namespaces. When the scan scope is NAMESPACE, this parameter cannot be empty. If the scan scope is REPO, you must specify a unique Namespace for this parameter.
	string	No	Namespace	prd
RepoNames	array	No	The list of repositories. When the scan scope is NAMESPACE, this parameter must be empty. When the scan scope is REPO, this parameter cannot be empty.
	string	No	The name of the repository.	prod
RepoTagFilterPattern	string	Yes	The tag filtering rules.	prod-.*

Response parameters

Parameter	Type	Description	Example
	object	The response struct.
RequestId	string	Request Id	33EF1695-E2B7-5D57-B4E1-3D655FE1EBD8
Code	long	The HTTP status code.	success
ScanRuleId	string	The rule ID.	crscnr-3qmkeiuggfpjkfrq

Examples

Sample success responses

JSONformat

{
  "RequestId": "33EF1695-E2B7-5D57-B4E1-3D655FE1EBD8",
  "Code": 0,
  "ScanRuleId": "crscnr-3qmkeiuggfpjkfrq"
}

Error codes

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

Change history

Change time	Summary of changes	Operation
2025-11-28	Add Operation	View Change Details