supabase_vault
Supabase Vault Extension
Overview
| Package | Version | Category | License | Language |
|---|---|---|---|---|
pg_vault | 0.3.1 | SEC | Apache-2.0 | C |
| ID | Extension | Bin | Lib | Load | Create | Trust | Reloc | Schema |
|---|---|---|---|---|---|---|---|---|
| 7050 | supabase_vault | No | Yes | No | Yes | No | No | vault |
Version
| Type | Repo | Version | PG Ver | Package | Deps |
|---|---|---|---|---|---|
| EXT | PIGSTY | 0.3.1 | 1817161514 | pg_vault | pgsodium |
| RPM | PIGSTY | 0.3.1 | 1817161514 | vault_$v | - |
| DEB | PIGSTY | 0.3.1 | 1817161514 | postgresql-$v-vault | - |
Build
You can build the RPM / DEB packages for pg_vault using pig build:
Install
You can install pg_vault directly. First, make sure the PGDG and PIGSTY repositories are added and enabled:
Install the extension using pig or apt/yum/dnf:
Install
pig
dnf
apt
Create Extension:
Usage
Supabase Vault provides a vault.secrets table to store sensitive information (API keys, tokens, etc.) encrypted at rest. Decryption happens on the fly through the vault.decrypted_secrets view.
Storing Secrets
Reading Secrets
The vault.secrets table stores data encrypted. Use the vault.decrypted_secrets view to read decrypted values:
Updating Secrets
Security Note
Turn off statement logging to prevent secrets from appearing in logs:
Was this page helpful?
Thanks—your feedback helps us improve this page.
What got in the way? (optional)