Export from Cloud Firestore to Azure Blob Storage

CloudQuery is an open-source data integration platform that allows you to export data from any source to any destination.

The CloudQuery Cloud Firestore plugin allows you to sync data from Cloud Firestore to any destination, including Azure Blob Storage. It's free, open source, requires no account, and takes only minutes to get started.

Ready? Let's dive right in!

Step 1. Install the CloudQuery CLI

The CloudQuery CLI is a command-line tool that runs the sync. It supports MacOS, Linux and Windows.

brew install cloudquery/tap/cloudquery

Step 2. Configure the Cloud Firestore source plugin

Create a configuration file for the Cloud Firestore plugin and set up authentication.

Configuration

Create a file called firestore.yaml and add the following contents:

kind: source
spec:
  # Source spec section
  name: firestore
  path: cloudquery/firestore
  version: "v1.0.2"
  tables: ["*"]
  destinations: ["azblob"]
  spec:
    # Firestore specific configuration goes here

Fine-tune this configuration to match your needs. For more information, see the Cloud Firestore Plugin ↗ page in the docs.

Authentication

The Firestore plugin authenticates using your Application Default Credentials (opens in a new tab). Available options are all the same options described here (opens in a new tab) in detail:

Local Environment:

gcloud auth application-default login (recommended when running locally)

Google Cloud cloud-based development environment:

When you run on Cloud Shell or Cloud Code credentials are already available.

Google Cloud containerized environment:

When running on GKE use workload identity (opens in a new tab).

Google Cloud services that support attaching a service account (opens in a new tab):

Services such as Compute Engine, App Engine and functions supporting attaching a user-managed service account which will CloudQuery will be able to utilize.

On-premises or another cloud provider

The suggested way is to use Workload identity federation (opens in a new tab)
If not available you can always use service account keys and export the location of the key via GOOGLE_APPLICATION_CREDENTIALS. Highly not recommended as long-lived keys are a security risk

Step 3. Configure the Azure Blob Storage destination plugin

Create a configuration file for the Azure Blob Storage plugin and set up authentication.

Configuration

Create a file called azblob.yaml and add the following contents:

kind: destination
spec:
  name: "azblob"
  path: "cloudquery/azblob"
  version: "v3.2.0"
  write_mode: "append" # this plugin only supports 'append' mode
  # batch_size: 10000 # optional
  # batch_size_bytes: 5242880 # optional
  spec:
    storage_account: "cqdestinationazblob"
    container: "test"
    path: "path/to/files"
    format: "parquet" # options: parquet, json, csv

Fine-tune this configuration to match your needs. For more information, see the Azure Blob Storage Plugin ↗ page in the docs.

Authentication

The plugin needs to be authenticated with your Azure account in order to fetch information about your cloud setup.

You can either authenticate with az login (when running locally), or by using a "service principal" and exporting environment variables (appropriate for automated deployments).

You can find out more about authentication with Azure at Azure's documentation (opens in a new tab) for the Go SDK.

Step 4. Start the Sync

Run the following command in your terminal to start the sync

cloudquery sync firestore.yaml azblob.yaml

And away we go! 🚀 The sync will run until completion, fetching all selected tables from Cloud Firestore. Any errors will be logged to a file called cloudquery.log.

Export from Cloud Firestore to Azure Blob Storage

Step 1. Install the CloudQuery CLI

Step 2. Configure the Cloud Firestore source plugin

Configuration

Authentication

Step 3. Configure the Azure Blob Storage destination plugin

Configuration

Authentication

Step 4. Start the Sync

Further Reading