fix(firestore-bigquery-export): remove multiple database support

Author: cabljac

firestore-bigquery-export/CHANGELOG.md

@@ -2,6 +2,8 @@
 
 fixed - medium npm vulnerabilities
 
+fixed - rollback broken multiple database parameter option
+
 ## Version 0.1.50
 
 fixed - fixed timestamp as a fieldname partitioning

firestore-bigquery-export/README.md

@@ -124,8 +124,6 @@ To install an extension, your project must be on the [Blaze (pay as you go) plan
 
 * BigQuery Project ID: Override the default project for BigQuery instance. This can allow updates to be directed to to a BigQuery instance on another GCP project.
 
-* Database ID: Override the default project Firestore database. Learn more about managing multiple Firestore databases [here](https://cloud.google.com/firestore/docs/manage-databases).
-
 * Collection path: What is the path of the collection that you would like to export? You may use `{wildcard}` notation to match a subcollection of all documents in a collection (for example: `chatrooms/{chatid}/posts`). Parent Firestore Document IDs from `{wildcards}`  can be returned in `path_params` as a JSON formatted string.
 
 * Enable Wildcard Column field with Parent Firestore Document IDs: If enabled, creates a column containing a JSON object of all wildcard ids from a documents path.

firestore-bigquery-export/extension.yaml

@@ -189,16 +189,6 @@ params:
     default: ${PROJECT_ID}
     required: true
 
-  - param: DATABASE_ID
-    label: Database ID
-    description: >-
-      Override the default project Firestore database. Learn more about managing
-      multiple Firestore databases
-      [here](https://cloud.google.com/firestore/docs/manage-databases).
-    type: string
-    default: (default)
-    required: true
-
   - param: COLLECTION_PATH
     label: Collection path
     description: >-

firestore-bigquery-export/functions/src/config.ts

@@ -33,7 +33,7 @@ export function clustering(clusters: string | undefined) {
 
 export default {
   bqProjectId: process.env.BIGQUERY_PROJECT_ID,
-  databaseId: process.env.DATABASE_ID || "(default)",
+  databaseId: "(default)",
   collectionPath: process.env.COLLECTION_PATH,
   datasetId: process.env.DATASET_ID,
   doBackfill: process.env.DO_BACKFILL === "yes",