List Federations

dataproc_metastore.list_federations
ActionGoogle Cloudconnection required

Calls Dataproc Metastore GET /v1/projects/{projectsId}/locations/{locationsId}/federations.

Lists federations in a project and location.

Connection

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

Configuration

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

FieldTypeRequiredDefaultConstraintsExample
project_id
GCP project id (overrides connection).
stringNo———
location
Location / region (overrides connection).
stringNo———
filter
Optional. The filter to apply to list results.
stringNo———
order_by
Optional. Specify the ordering of results as described in Sorting Order (https://cloud.google.com/apis/design/
stringNo———
page_size
Optional. The maximum number of federations to return.
numberNo50≥ 1—
page_token
Optional. A page token, received from a previous ListFederationServices call. Provide this token to retrieve t
stringNo———

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "page_size": 50
}

Output

One shape.

result

FieldTypeExample
ok
boolean—
federations
array—
unreachable
array—
nextPageToken
string—
{
  "federations": [],
  "nextPageToken": "",
  "ok": false,
  "unreachable": []
}

See List Federations run in a workflow.

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