Table: vercel_secret
Secrets are a legacy way to encrypt variables in Vercel, and have been deprecated. All environment variables are now encrypted by default.
Examples
List all secrets
select project_id, name, uid, created_atfrom vercel_secret;
Secrets more than 1 year old
select project_id, name, uid, created_atfrom vercel_secretwhere created_at < now() - interval '1 year';
Secrets used by environment variables
select p.name as project_name, e ->> 'key' as env_var, e ->> 'type' as env_var_type, s.name as secret_name, s.uid as secret_uid, s.created_at as secret_created_atfrom vercel_project as p, jsonb_array_elements(env) as e, vercel_secret as swhere e ->> 'type' = 'secret' and e ->> 'value' = s.uid;
.inspect vercel_secret
Secrets in the Vercel account.
Name | Type | Description |
---|---|---|
_ctx | jsonb | Steampipe context in JSON form, e.g. connection_name. |
created_at | timestamp with time zone | Time when the secret was created. |
decryptable | boolean | True if the secret value can be decrypted after it is created. |
name | text | Name of the secret. |
project_id | text | Unique identifier of the project the secret belongs to. |
team_id | text | Unique identifier of the team the secret was created for. |
uid | text | Unique identifier of the secret. |
user_id | text | Unique identifier of the user who created the secret. |
value | text | Value of the secret. |