Create Catalog
biglake.create_catalog
ActionGoogle Cloudconnection required
Calls biglake v1 POST /v1/projects/{projectsId}/locations/{locationsId}/catalogs.
Creates a new catalog.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Lakehouse
- 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.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
location Location or region; taken from the connection when unset. | string | No | — | — | — |
body The Catalog resource, as the API defines it. | object | Yes | — | — | — |
catalog_id The ID to use for the catalog, which will become the final component of the catalog's resource name. Required. | string | Yes | — | — | — |
Output
One shape.
result
Extra keys beyond the ones listed can appear.
| Field | Type | Example |
|---|---|---|
createTime | string | — |
deleteTime | string | — |
expireTime | string | — |
name | string | — |
updateTime | string | — |
{
"createTime": "",
"deleteTime": "",
"expireTime": "",
"name": "",
"updateTime": ""
}Related Google Lakehouse nodes
See Create Catalog run in a workflow.
In a technical demo we add the Google Lakehouse connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.