Update Data Policy

bigquery_data_policy.update_data_policy
ActionGoogle Cloudconnection required

Calls bigquerydatapolicy v2 PATCH /v2/projects/{projectsId}/locations/{locationsId}/dataPolicies/{dataPoliciesId}.

Updates the metadata for an existing data policy.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Google BigQuery Data Policy
Secret shape
{"client_id", "client_secret", "refresh_token"}
Config it needs
project_id, location
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
location
Location or region; taken from the connection when unset.
stringNo———
data_policy
Data policy name or id.
stringYes———
body
The DataPolicy resource, as the API defines it.
objectYes———

Output

One shape.

result

Extra keys beyond the ones listed can appear.

FieldTypeExample
dataGovernanceTag
object—
dataMaskingPolicy
object—
dataPolicyId
string—
dataPolicyType
string—
etag
string—
grantees
array—
name
string—
policyTag
string—
version
string—
{
  "dataGovernanceTag": {},
  "dataMaskingPolicy": {},
  "dataPolicyId": "",
  "dataPolicyType": "",
  "etag": "",
  "grantees": [],
  "name": "",
  "policyTag": "",
  "version": ""
}

See Update Data Policy run in a workflow.

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