fix(firestore-bigquery-export): kit/extension parity – kit ignores the migrated ingress setting on the Firestore trigger #3304

firestore-bigquery-export kit/extension parity. Priority: low. The trigger still runs, but an ingress setting the user chose on the extension is silently dropped.

Difference

On the extension, ingress was an install-time setting. ext:migrate carries it over through setGlobalOptions, but the kit pins ingressSettings: "ALLOW_INTERNAL_ONLY" on fsexportbigquery, and a function-level option always wins over a global one.

The task functions (syncBigQuery, initBigQuerySync and the other lifecycle task) don't pin ingress, so the migrated global value applies to them.

Code

• Kit: EVENT_FUNCTION_OPTIONS pins ingress (index.ts#L175-L181), used by fsexportbigquery (#L204-L211).
• README says ingress matches the extension and doesn't list this as a difference (README.md#L361-L368).

Resolution

Only default ingress, so the migrated global value wins when set:

import { __getSpec } from "firebase-functions/v2/options";
// …
  ingressSettings:
    __getSpec().globalOptions.ingressSettings ?? "ALLOW_INTERNAL_ONLY",

__getSpec is marked @alpha. If we keep the pin instead, add it to the README's differences. Same issue raised for delete-user-data in #3276 (comment).