Update Scan Config

web_security_scanner.update_scan_config
ActionGoogle Cloudconnection required

Calls websecurityscanner v1 PATCH /v1/projects/{projectsId}/scanConfigs/{scanConfigsId}.

Updates a ScanConfig.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Google Web Security Scanner
Secret shape
{"client_id", "client_secret", "refresh_token"}
Config it needs
project_id
Resolved by
config.connection_id, else node.connection_id

Configuration

3 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
scan_config
Scan config name or id.
stringYes———
body
The ScanConfig resource, as the API defines it.
objectYes———
update_mask
The update mask applies to the resource. Optional.
stringNo———

Output

One shape.

result

Extra keys beyond the ones listed can appear.

FieldTypeExample
authentication
object—
blacklistPatterns
array—
displayName
string—
exportToSecurityCommandCenter
string—
ignoreHttpStatusErrors
boolean—
latestRun
object—
managedScan
boolean—
maxQps
integer—
name
string—
riskLevel
string—
schedule
object—
startingUrls
array—
staticIpScan
boolean—
targetPlatforms
array—
userAgent
string—
{
  "authentication": {},
  "blacklistPatterns": [],
  "displayName": "",
  "exportToSecurityCommandCenter": "",
  "ignoreHttpStatusErrors": false,
  "latestRun": {},
  "managedScan": false,
  "maxQps": 0,
  "name": "",
  "riskLevel": "",
  "schedule": {},
  "startingUrls": [],
  "staticIpScan": false,
  "targetPlatforms": [],
  "userAgent": ""
}

See Update Scan Config run in a workflow.

In a technical demo we add the Google Web Security Scanner connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.