firestore-bigquery-export Collection path 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: _ Version 0.1.5
• Configuration values (redact info where appropriate):
  • Collection path: foo/{slug}/collection/document

[REQUIRED] Step 3: Describe the problem

I’m trying to setup this extension to sync a sub-collection with the collection path noted above. During installation I get the following error.

Error occurred while deploying resources: RESOURCE_ERROR: /deployments/firebase-ext-firestore-bigquery-export-discovery/resources/fsexportbigquery Deployment Field Violation Error: gcp-types/cloudfunctions-v1:projects.locations.functions: INVALID_ARGUMENT: Field: event_trigger (Expected value foo/{slug}/collection/document/{documentId} to match regular expression [^/]+/[^/]+(/[^/]+/[^/]+)*)

[deplorableword]

@russellwheatley Gotcha! A possible improvement would be to make the regex error mention the word document, I think that might make it easier for everyone to debug 😀

[russellwheatley]

@deplorableword You’re correct, thank you for bringing this to my attention! It isn’t possible to do wildcards via a Firestore query. But this isn’t a typical Firestore query, it is a cloud function that listens to documents as described here.

The reason why it failed initially is because you don’t have to specify the document part of the path, it is interpolated into a string with documentId on the path already. See here. I’ll close this PR.

Apologies for the confusion!