All Products
Search
Document Center

Security Center:CreateVulAutoRepairConfig

Last Updated:Nov 25, 2024

Creates a list of vulnerabilities that can be automatically fixed. After the list is created, you can select the list when you create a vulnerability fixing task on the Playbook page.

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.

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.
OperationAccess levelResource typeCondition keyAssociated operation
yundun-sas:CreateVulAutoRepairConfigcreate
*All Resources
*
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
TypestringYes

The type of the vulnerability. Valid values: -cve: Linux software vulnerability -sys: Windows system vulnerability

cve
VulAutoRepairConfigListarray<object>Yes

The vulnerabilities that can be automatically fixed.

objectYes

The vulnerability that can be automatically fixed.

AliasNamestringYes

The alias of the vulnerability.

CVE-2018-25032:zlib 1.2.11 memory corruption
NamestringYes

The name of the vulnerability.

anolisos:8.4:ANSA-2022:0001
ReasonstringNo

The reason why the vulnerability can be automatically fixed.

TestAutoRepair

Response parameters

ParameterTypeDescriptionExample
object
RequestIdstring

The ID of the request, which is used to locate and troubleshoot issues.

6673D49C-A9AB-40DD-B4A2-B92306701AE7
Successboolean

Indicates whether the request was successful. Valid values:

  • true: The request was successful.
  • false: The request failed.
true
Codestring

The status code returned. The status code 200 indicates that the request was successful. Other status codes indicate that the request failed. You can identify the cause of the failure based on the status code.

200
Messagestring

The error message returned.

success
HttpStatusCodeinteger

The HTTP status code returned.

200

Examples

Sample success responses

JSONformat

{
  "RequestId": "6673D49C-A9AB-40DD-B4A2-B92306701AE7",
  "Success": true,
  "Code": "200",
  "Message": "success",
  "HttpStatusCode": 200
}

Error codes

HTTP status codeError codeError messageDescription
400InnerErrorInnerError-
400IllegalParamIllegal param-
403NoPermissioncaller has no permissionYou are not authorized to do this operation.
500ServerErrorServerError-

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

Change history

Change timeSummary of changesOperation
No change history