Update Data Store

discovery_engine.update_data_store
ActionGoogle Cloudconnection required

Calls discoveryengine v1 PATCH /v1/projects/{projectsId}/locations/{locationsId}/dataStores/{dataStoresId}.

Updates a DataStore.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Google Discovery Engine
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_store
Data store name or id.
stringYes———
body
The GoogleCloudDiscoveryengineV1DataStore resource, as the API defines it.
objectYes———

Output

One shape.

result

Extra keys beyond the ones listed can appear.

FieldTypeExample
aclEnabled
boolean—
advancedSiteSearchConfig
object—
billingEstimation
object—
cmekConfig
object—
configurableBillingApproach
string—
configurableBillingApproachUpdateTime
string—
contentConfig
string—
createTime
string—
defaultSchemaId
string—
displayName
string—
documentProcessingConfig
object—
federatedSearchConfig
object—
healthcareFhirConfig
object—
identityMappingStore
string—
industryVertical
string—
isInfobotFaqDataStore
boolean—
kmsKeyName
string—
name
string—
naturalLanguageQueryUnderstandingConfig
object—
servingConfigDataStore
object—
solutionTypes
array—
startingSchema
object—
workspaceConfig
object—
{
  "aclEnabled": false,
  "advancedSiteSearchConfig": {},
  "billingEstimation": {},
  "cmekConfig": {},
  "configurableBillingApproach": "",
  "configurableBillingApproachUpdateTime": "",
  "contentConfig": "",
  "createTime": "",
  "defaultSchemaId": "",
  "displayName": "",
  "documentProcessingConfig": {},
  "federatedSearchConfig": {},
  "healthcareFhirConfig": {},
  "identityMappingStore": "",
  "industryVertical": "",
  "isInfobotFaqDataStore": false,
  "kmsKeyName": "",
  "name": "",
  "naturalLanguageQueryUnderstandingConfig": {},
  "servingConfigDataStore": {},
  "solutionTypes": [],
  "startingSchema": {},
  "workspaceConfig": {}
}

See Update Data Store run in a workflow.

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