Who can read your Vercel Edge Config, and is anything checking it
Use “Who can read your Vercel Edge Config, and is anything checking it” in Recued. THE token list hands back THE whole token. It reads information without changing data in the connected service.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (27 steps)
configs_raw
?
configs
default
Apply default
have_configs
template
Generate text from a template
fail: step.configs is_empty
config_count
count
Count items in configs
requested_config
trim
Trim whitespace from setting edge config id
first_config_id
default
Apply default
target_config
default
Apply default
unschemad
filter
Filter by condition
unschemad_count
count
Count items in unschemad
schemad
filter
Filter by condition
schemad_count
count
Count items in schemad
deleted_configs
filter
Filter by condition
deleted_count
count
Count items in deleted configs
total_items
sum
Sum values in
total_bytes
sum
Sum values in
tokens_raw
?
tokens
default
Apply default
token_count
count
Count items in tokens
unlabelled_tokens
filter
Filter by condition
unlabelled_count
count
Count items in unlabelled tokens
backups_raw
?
backups
default
Apply default
backup_count
count
Count items in backups
has_backups
compare
Check if backup count is greater than 0
card
to_summary
Format results as a summary card
config_table
to_table
Format results as a data table
token_table
to_table
Format results as a data table
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
vercel
setting
=
edge config id
setting
=
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.