Skip to content

Commit

Permalink
BigQuery Authorized datasets (#5700) (#192)
Browse files Browse the repository at this point in the history
* Add authorized views to bigquery_dataset

* Add authorized view to dataset_access

* Fix test file

* Add required to nested dataset field

Signed-off-by: Modular Magician <magic-modules@google.com>
  • Loading branch information
modular-magician authored Feb 11, 2022
1 parent 5630ec1 commit 40cef37
Show file tree
Hide file tree
Showing 4 changed files with 158 additions and 0 deletions.
15 changes: 15 additions & 0 deletions bigquery_dataset_authorized_dataset/backing_file.tf
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
# This file has some scaffolding to make sure that names are unique and that
# a region and zone are selected when you try to create your Terraform resources.

locals {
name_suffix = "${random_pet.suffix.id}"
}

resource "random_pet" "suffix" {
length = 2
}

provider "google" {
region = "us-central1"
zone = "us-central1-c"
}
57 changes: 57 additions & 0 deletions bigquery_dataset_authorized_dataset/main.tf
Original file line number Diff line number Diff line change
@@ -0,0 +1,57 @@
resource "google_bigquery_dataset" "public" {
dataset_id = "public-${local.name_suffix}"
friendly_name = "test"
description = "This dataset is public"
location = "EU"
default_table_expiration_ms = 3600000

labels = {
env = "default"
}

access {
role = "OWNER"
user_by_email = google_service_account.bqowner.email
}

access {
role = "READER"
domain = "hashicorp.com"
}
}

resource "google_bigquery_dataset" "dataset" {
dataset_id = "private-${local.name_suffix}"
friendly_name = "test"
description = "This dataset is private"
location = "EU"
default_table_expiration_ms = 3600000

labels = {
env = "default"
}

access {
role = "OWNER"
user_by_email = google_service_account.bqowner.email
}

access {
role = "READER"
domain = "hashicorp.com"
}

access {
dataset {
dataset {
project_id = google_bigquery_dataset.public.project
dataset_id = google_bigquery_dataset.public.dataset_id
}
target_types = ["VIEWS"]
}
}
}

resource "google_service_account" "bqowner" {
account_id = "bqowner-${local.name_suffix}"
}
7 changes: 7 additions & 0 deletions bigquery_dataset_authorized_dataset/motd
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
===

These examples use real resources that will be billed to the
Google Cloud Platform project you use - so make sure that you
run "terraform destroy" before quitting!

===
79 changes: 79 additions & 0 deletions bigquery_dataset_authorized_dataset/tutorial.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,79 @@
# Bigquery Dataset Authorized Dataset - Terraform

## Setup

<walkthrough-author name="rileykarson@google.com" analyticsId="UA-125550242-1" tutorialName="bigquery_dataset_authorized_dataset" repositoryUrl="https://github.com/terraform-google-modules/docs-examples"></walkthrough-author>

Welcome to Terraform in Google Cloud Shell! We need you to let us know what project you'd like to use with Terraform.

<walkthrough-project-billing-setup></walkthrough-project-billing-setup>

Terraform provisions real GCP resources, so anything you create in this session will be billed against this project.

## Terraforming!

Let's use {{project-id}} with Terraform! Click the Cloud Shell icon below to copy the command
to your shell, and then run it from the shell by pressing Enter/Return. Terraform will pick up
the project name from the environment variable.

```bash
export GOOGLE_CLOUD_PROJECT={{project-id}}
```

After that, let's get Terraform started. Run the following to pull in the providers.

```bash
terraform init
```

With the providers downloaded and a project set, you're ready to use Terraform. Go ahead!

```bash
terraform apply
```

Terraform will show you what it plans to do, and prompt you to accept. Type "yes" to accept the plan.

```bash
yes
```


## Post-Apply

### Editing your config

Now you've provisioned your resources in GCP! If you run a "plan", you should see no changes needed.

```bash
terraform plan
```

So let's make a change! Try editing a number, or appending a value to the name in the editor. Then,
run a 'plan' again.

```bash
terraform plan
```

Afterwards you can run an apply, which implicitly does a plan and shows you the intended changes
at the 'yes' prompt.

```bash
terraform apply
```

```bash
yes
```

## Cleanup

Run the following to remove the resources Terraform provisioned:

```bash
terraform destroy
```
```bash
yes
```

0 comments on commit 40cef37

Please sign in to comment.