Repository navigation
decision(firestore-send-email): kit/extension parity – config log keys and resource labels differ #3302
Description
firestore-send-email kit/extension parity. Priority: low. Log-based metrics, alerts and billing reports built for the extension won't match the kit.
Difference
| Extension | Kit | |
|---|---|---|
| Startup config log keys | database, TTLExpireType, TTLExpireValue, tls, port, secure, authenticationType, location |
databaseId, ttlExpireType, ttlExpireValue, tlsOptions, oauthPort, oauthSecure, authType; no location |
| Unset secrets in that log | always "<omitted>" |
key left out (which shows what is configured) |
| When it's logged | once at module load | inside the first request |
| Resource and log labels | goog-firebase-ext, goog-firebase-ext-iid, goog-dm |
firebase-functions-codebase, firebase-functions-hash |
| Unknown TTL error text | Unknown TTLExpireType: … |
Unknown TTL expire type: … |
Reproduced
Compared the Initializing extension with configuration entries and the function labels on both deployed instances.
Code
- Extension: logs.ts#L21-L31, index.ts#L39
- Kit: logs.ts#L20-L36, index.ts#L88
Resolution
Options:
- Keep the extension's log keys and
<omitted>placeholders. - Or record the difference as accepted under "Decisions" in
firestore-send-emailkit tracking issue #3290 and list the renamed keys and labels in the README.
Activity
firestore-send-emailkit tracking issue #3290