firestore-bigquery-export Collection path (single depth) regex error

[READ] Step 1: Are you in the right place?

Issues filed here should be about bugs for a specific extension in this repository. If you have a general question, need help debugging, or fall into some other category use one of these other channels:

• For general technical questions, post a question on StackOverflow with the firebase tag.
• For general Firebase discussion, use the firebase-talk google group.
• To file a bug against the Firebase Extensions platform, or for an issue affecting multiple extensions, please reach out to Firebase support directly.

[REQUIRED] Step 2: Describe your configuration

• Extension name: _ firestore-bigquery-export
• Extension version: _ 0.1.7
• Configuration values (redact info where appropriate):

[REQUIRED] Step 3: Describe the problem

I am trying to export the entire firestre collection named events to BigQuery, but upon saving the above configuration am faced with the following error:

; RESOURCE_ERROR at /deployments/firebase-ext-firestore-bigquery-export/resources/fsexportbigquery: {"ResourceType":"gcp-types/cloudfunctions-v1:projects.locations.functions","ResourceErrorCode":"400","ResourceErrorMessage":{"code":400,"message":"The request has errors","status":"INVALID_ARGUMENT","details":[{"@type":"type.googleapis.com/google.rpc.BadRequest","fieldViolations":[{"field":"event_trigger","description":"Expected value /events/{documentId} to match regular expression [^/]+/[^/]+(/[^/]+/[^/]+)*"}]}],"statusMessage":"Bad Request","requestPath":"https://cloudfunctions.googleapis.com/v1/projects/lovecaster-f3c68/locations/us-central1/functions/ext-firestore-bigquery-export-fsexportbigquery","httpMethod":"PATCH"}}

---

Not sure if I’m doing something wrong or if #418 introduced this problem.

[laurenzlong]

Yes that is indeed a bug! Thanks for letting us know, I’ve filed an issue internally (bug ID 166473495) Since it’s an issue with the platform not the extension itself, we don’t track it in this repo.

[nwparker]

Yes that is indeed a bug! Thanks for letting us know, I’ve filed an issue internally (bug ID 166473495) Since it’s an issue with the platform not the extension itself, we don’t track it in this repo.

Thanks!