Authenticate Astro to GCP

Prerequisites

• A user account on GCP with access to GCP cloud resources.
• The Google Cloud SDK.
• The Astro CLI.
• An Astro project.
• Optional. Access to a secrets backend hosted on GCP, such as GCP Secret Manager.

Retrieve GCP user credentials locally

Run the following command to obtain your user credentials locally:

1
gcloud auth application-default login

The SDK provides a link to a webpage where you can log in to your Google Cloud account. After you complete your login, the SDK stores your user credentials in a file named application_default_credentials.json.

The location of this file depends on your operating system:

• Linux: $HOME/.config/gcloud/application_default_credentials.json
• Mac: /Users/<username>/.config/gcloud/application_default_credentials.json
• Windows: %APPDATA%/gcloud/application_default_credentials.json

Configure your Astro project

The Astro CLI runs Airflow in a Docker-based environment. To give Airflow access to your credential file, mount it as a Docker volume.

1. In your Astro project, create a file named docker-compose.override.yml to your project with the following configuration:

1
version: "3.1"
2
services:
3
  scheduler:
4
    volumes:
5
      - /Users/<username>/.config/gcloud/application_default_credentials.json:/usr/local/airflow/gcloud/application_default_credentials.json:rw
6
  webserver:
7
    volumes:
8
      - /Users/<username>/.config/gcloud/application_default_credentials.json:/usr/local/airflow/gcloud/application_default_credentials.json:rw
9
  triggerer:
10
    volumes:
11
      - /Users/<username>/.config/gcloud/application_default_credentials.json:/usr/local/airflow/gcloud/application_default_credentials.json:rw

2. In your Astro project’s .env file, add the following environment variable. Ensure that this volume path is the same as the one you configured in docker-compose.override.yml.

GOOGLE_APPLICATION_CREDENTIALS=/usr/local/airflow/gcloud/application_default_credentials.json

When you run Airflow locally, all GCP connections without defined credentials automatically fall back to your user credentials when connecting to GCP. Airflow applies and overrides user credentials for GCP connections in the following order:

• Mounted user credentials in the /~/gcloud/ folder
• Configurations in gcp_keyfile_dict
• An explicit username & password provided in the connection

For example, if you completed the configuration in this document and then created a new GCP connection with its own username and password, Airflow would use those credentials instead of the credentials in ~/gcloud/application_default_credentials.json.

Test your credentials with a secrets backend

Now that Airflow has access to your user credentials, you can use them to connect to your cloud services. Use the following example setup to test your credentials by pulling values from different secrets backends.

1. Create a secret for an Airflow variable or connection in GCP Secret Manager. You can do this using the Google Cloud Console or the gcloud CLI. All Airflow variables and connection keys must be prefixed with the following strings respectively:

   • airflow-variables-<my_variable_name>
   • airflow-connections-<my_connection_name>

   For example when adding the secret variable my_secret_var you will need to give the secret the name airflow-variables-my_secret_var.

2. Add the following environment variables to your Astro project .env file. For additional configuration options, see the Apache Airflow documentation. Make sure to specify your project_id.

   AIRFLOW__SECRETS__BACKEND=airflow.providers.google.cloud.secrets.secret_manager.CloudSecretManagerBackend
   AIRFLOW__SECRETS__BACKEND_KWARGS={"connections_prefix": "airflow-connections", "variables_prefix": "airflow-variables", "project_id": "<my-project-id>"}

3. Run the following command to start Airflow locally:

   1
   astro dev start

4. Access the Airflow UI at localhost:8080 and create an Airflow GCP connection named gcp_standard with no credentials. See Connections.

   When you use this connection in your dag, it will fall back to using your configured user credentials.

5. Add a dag which uses the secrets backend to your Astro project dags directory. You can use the following example dag to retrieve <my_variable_name> and <my_connection_id> from the secrets backend and print it to the terminal:

   1
   from airflow.models.dag import DAG
   2
   from airflow.hooks.base import BaseHook
   3
   from airflow.models import Variable
   4
   from airflow.decorators import task
   5
   from datetime import datetime
   6
   7
   with DAG(
   8
       'example_secrets_dag',
   9
       start_date=datetime(2022, 1, 1),
   10
       schedule=None
   11
   ):
   12
   13
       @task
   14
       def print_var():
   15
           my_var = Variable.get("<my_variable_name>")
   16
           print(f"My secret variable is: {my_var}")
   17
   18
           conn = BaseHook.get_connection(conn_id="<my_connection_name>")
   19
           print(f"My secret connection is: {conn.get_uri()}")
   20
   21
       print_var()

6. In the Airflow UI, unpause your dag and click Play to trigger a dag run.

7. View logs for your dag run. If the connection was successful, your masked secrets appear in your logs. See Airflow logging.