Get Catalog
biglake.get_catalog
ActionGoogle Cloudconnection required
Calls Lakehouse GET /v1/projects/{projectsId}/locations/{locationsId}/catalogs/{catalogsId}.
Gets the catalog specified by the resource name.
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
- location, project_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, 1 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 |
|---|---|---|---|---|---|
project_id GCP project id (overrides connection). | string | No | — | — | — |
location Location / region (overrides connection). | string | No | — | — | — |
catalog Id of the catalog to act on, from biglake.list_catalogs — not its name. | string | Yes | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
name | string | — |
expireTime | string | — |
updateTime | string | — |
createTime | string | — |
deleteTime | string | — |
{
"createTime": "",
"deleteTime": "",
"expireTime": "",
"name": "",
"ok": false,
"updateTime": ""
}Related Google Lakehouse nodes
See Get 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.