Type-safe key registry for getSecret — empty by default, populated by
declaration merging (module augmentation). When it has no members, getSecret
accepts any string (the loose default); once keys are merged in, getSecret
narrows to exactly those keys, giving editor autocomplete and a compile error on
a typo. Nothing else changes — the value is still fetched from Secrets Manager at
runtime.
You normally never write this by hand: npm run typegen scans your app's
secret('...') calls and generates a .d.ts that augments it. To do it manually:
Type-safe key registry for getSecret — empty by default, populated by declaration merging (module augmentation). When it has no members,
getSecretaccepts anystring(the loose default); once keys are merged in,getSecretnarrows to exactly those keys, giving editor autocomplete and a compile error on a typo. Nothing else changes — the value is still fetched from Secrets Manager at runtime.You normally never write this by hand:
npm run typegenscans your app'ssecret('...')calls and generates a.d.tsthat augments it. To do it manually:See
HostingConfigRegistry for the
config()/getConfigcounterpart.