How-to guideApplies to: Unified engine deployments
Create a new reference fixed to one existing remote secret version.
Before you start
Configure recipe_sm using the provider setup recipe.
Store raw bearer-token text for an existing Iceberg REST catalog in the selected
secret. Use a valid existing version ID supplied by Secrets Manager. The engine
and workers need access to the catalog and its table files. The catalog must
supply temporary storage credentials or the table location must already be
configured.
Values to collect
- Remote secret name, exact version, catalog API URI, warehouse, namespace, and
table.
Run the SQL
Replace every <placeholder> before running. Use unused names for the resources
below. Run the statements in order in Workbench.
Check the result
The SELECT should return up to five rows from the chosen table. Use a nonempty
table for this check. This verifies both metadata and table-file access;
creating the registration alone does not verify either. DESCRIBE should show the
pinned reference without returning token text.
Clean up
This removes only the Unified registrations. It leaves the remote catalog and
its tables in place.
Last modified on November 4, 2026