How-to guideApplies to: Unified engine deployments
Create a named reference and use its value through a matching credential.
Before you start
Have an administrator configure the engine provider alias recipe_file before
running SQL. Configure type file with files = { catalog_token =
“/run/credentials/catalog-token” }. Mount the token file on the secret-service
host. SQL selects the mapping name; it does not accept an arbitrary file path.
See
provider configuration.
The selected value must be raw bearer-token text accepted by an existing Iceberg
REST catalog. Have its API URI, warehouse, namespace, and nonempty table ready.
The service must provide usable temporary storage credentials or already
configured storage access.
Values to collect
- A configured provider alias, secret identifier, and the data connection values
shown below.
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
DESCRIBE shows the provider reference, not its plaintext value. The SELECT
should return actual table or file rows and proves that the consumer can resolve
and use the selected secret.
Clean up
This removes only the Unified registrations. It leaves the remote catalog and
its tables in place.
The external secret value and its provider mapping are left in place.Last modified on November 4, 2026
