Pavel Jbanov
Pavel Jbanov
I changed the base of this PR -- all new changes need to go into `next`.
We actually don't set `ingressSettings` and that is the problem when org policies require them to be specified. It's most likely not an issue specific to bigquery extension. I'm not...
@RajvirBains Can you tell me if your org policy `constraints/cloudfunctions.allowedIngressSettings` includes `ALLOW_ALL`? (If you're not comfortable sharing this info here, you can file a [support ticket](https://firebase.google.com/support/troubleshooter/contact) with details and reference...
@RajvirBains I think you are correct -- for 1st gen cloud functions currently used by Firebase Extensions there is no public HTTP endpoint created for event triggers (ex. firestore triggers...
@RajvirBains The cloud functions trigger definitions are in the code. Here is the sample code changes and instructions for how to manually deploy the bigquery export function with a VPC...
Hmm... for some reason I wrongly assumed that for `ingressSettings: 'ALLOW_INTERNAL_ONLY'` it required a VPC connector. This may be a much simpler fix than I expected. Let me investigate whether...
I'm running some e2e tests. I can't provide a firm ETA, but this will take at least a couple of weeks to confirm and release. I'll provide another update ones...
Everything is in place, just not broadly enabled (still testing a few scenarios). If you can share your project id (through the support ticket) I can enable the ingress settings...
@RajvirBains your projects are allowlisted, you can give it a try.