Schedule production runs
This quickstart walks you through the following steps to schedule production runs in Dataform:
- Create a Dataform repository.
- Grant the required roles.
Create a release configuration and a workflow configuration.
Create a
productionrelease configuration and set the frequency of creatingproductioncompilation results. Then, create aproductionworkflow configuration, select theproductionrelease configuration, and set a schedule for runningproductioncompilation results.
Before you begin
- Sign in to your Google Cloud account. If you're new to Google Cloud, create an account to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.
-
In the Google Cloud console, on the project selector page, select or create a Google Cloud project.
Roles required to select or create a project
- Select a project: Selecting a project doesn't require a specific IAM role—you can select any project that you've been granted a role on.
-
Create a project: To create a project, you need the Project Creator role
(
roles/resourcemanager.projectCreator), which contains theresourcemanager.projects.createpermission. Learn how to grant roles.
-
Verify that billing is enabled for your Google Cloud project.
Enable the BigQuery and Dataform APIs.
Roles required to enable APIs
To enable APIs, you need the
serviceusage.services.enablepermission. If you created the project, then you likely already have this permission through the Owner role (roles/owner). Otherwise, you can get this permission through the Service Usage Admin role (roles/serviceusage.serviceUsageAdmin). Learn how to grant roles.-
In the Google Cloud console, on the project selector page, select or create a Google Cloud project.
Roles required to select or create a project
- Select a project: Selecting a project doesn't require a specific IAM role—you can select any project that you've been granted a role on.
-
Create a project: To create a project, you need the Project Creator role
(
roles/resourcemanager.projectCreator), which contains theresourcemanager.projects.createpermission. Learn how to grant roles.
-
Verify that billing is enabled for your Google Cloud project.
Enable the BigQuery and Dataform APIs.
Roles required to enable APIs
To enable APIs, you need the
serviceusage.services.enablepermission. If you created the project, then you likely already have this permission through the Owner role (roles/owner). Otherwise, you can get this permission through the Service Usage Admin role (roles/serviceusage.serviceUsageAdmin). Learn how to grant roles.
Additionally, select or create a custom service account to run workflows in BigQuery.
Required roles
To get the permissions that you need to perform all tasks in this quickstart, ask your administrator to grant you the following IAM roles:
- Dataform Admin (
roles/dataform.admin) on the repository - Service Account User (
roles/iam.serviceAccountUser) on the custom service account - Project IAM Admin (
roles/resourcemanager.projectIamAdmin) on the project
For more information about granting roles, see Manage access to projects, folders, and organizations.
You might also be able to get the required permissions through custom roles or other predefined roles.
Grant required roles
To run workflows in BigQuery, you can use a custom service account or your Google Account (Preview). However, custom service account credentials are the default option for scheduled runs. Using Google Account user account credentials is discouraged for scheduled runs.
Your custom service account must have the following required roles:
- BigQuery Data Editor
(
roles/bigquery.dataEditor) on projects or specific BigQuery datasets to which Dataform needs both read and write access. This usually includes the project hosting your Dataform repository. - BigQuery Data Viewer
(
roles/bigquery.dataViewer) on projects or specific BigQuery datasets to which Dataform needs read-only access. - BigQuery Job User
(
roles/bigquery.jobUser) on the project hosting your Dataform repository.
To let Dataform use your custom service account, the default Dataform service agent must have the following roles on the custom service account resource:
- Service Account Token Creator
(
roles/iam.serviceAccountTokenCreator) - Service Account User
(
roles/iam.serviceAccountUser)
To grant these roles, follow these steps:
In the Google Cloud console, go to the IAM page.
Click Grant access.
In the New principals field, enter your custom service account ID.
In the Select a role menu, select the following roles one by one, using Add another role for each additional role:
- BigQuery Data Editor
- BigQuery Data Viewer
- BigQuery Job User
Click Save.
In the Google Cloud console, go to the Service accounts page.
Select your custom service account.
Go to Principals with access, and then click Grant access.
In the New principals field, enter your default Dataform service agent ID.
Your default Dataform service agent ID is in the following format:
service-PROJECT_NUMBER@gcp-sa-dataform.iam.gserviceaccount.comReplace
PROJECT_NUMBERwith the numeral ID of your Google Cloud project. You can find your Google Cloud project ID in the Google Cloud console dashboard. For more information, see Find the project name, number, and ID.In the Select a role list, add the following roles:
- Service Account User
- Service Account Token Creator
Click Save.
For more information on granting roles, see Grant Dataform the required access.
Create a Dataform repository
In the Google Cloud console, go to the Dataform page.
Click Create repository.
On the Create repository page, do the following:
In the Repository ID field, enter
quickstart-production.In the Region list, select
europe-west4.In the Service account list, select a custom service account for the repository.
In the actAs permission checks section, enforce the permission checks on user actions on the repository.
Click Create.
Click Go to repositories.
Create a release configuration and workflow configuration
To create production compilation results of the quickstart-production
repository and schedule a run of production tables, follow these steps: