From ee6daa95403fdf9faaa7aad2f95e4126789e0fff Mon Sep 17 00:00:00 2001
From: Modular Magician <magic-modules@google.com>
Date: Tue, 18 Mar 2025 20:50:16 +0000
Subject: [PATCH] Add support for the managed disaster recovery feature in
 google_bigquery_reservation (#13381)

[upstream:8e6dfbb8be901a9dc7636d912f9c9726f283b122]

Signed-off-by: Modular Magician <magic-modules@google.com>
---
 .../backing_file.tf                           | 15 ++++
 .../main.tf                                   | 14 ++++
 .../motd                                      |  7 ++
 .../tutorial.md                               | 79 +++++++++++++++++++
 4 files changed, 115 insertions(+)
 create mode 100644 bigquery_reservation_with_disaster_recovery/backing_file.tf
 create mode 100644 bigquery_reservation_with_disaster_recovery/main.tf
 create mode 100644 bigquery_reservation_with_disaster_recovery/motd
 create mode 100644 bigquery_reservation_with_disaster_recovery/tutorial.md

diff --git a/bigquery_reservation_with_disaster_recovery/backing_file.tf b/bigquery_reservation_with_disaster_recovery/backing_file.tf
new file mode 100644
index 00000000..c60b1199
--- /dev/null
+++ b/bigquery_reservation_with_disaster_recovery/backing_file.tf
@@ -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"
+}
diff --git a/bigquery_reservation_with_disaster_recovery/main.tf b/bigquery_reservation_with_disaster_recovery/main.tf
new file mode 100644
index 00000000..f2670e7a
--- /dev/null
+++ b/bigquery_reservation_with_disaster_recovery/main.tf
@@ -0,0 +1,14 @@
+resource "google_bigquery_reservation" "reservation" {
+  name           = "my-reservation-${local.name_suffix}"
+  location       = "us-west2"
+  secondary_location = "us-west1"
+  // Set to 0 for testing purposes
+  // In reality this would be larger than zero
+  slot_capacity     = 0
+  edition = "ENTERPRISE_PLUS"
+  ignore_idle_slots = true
+  concurrency       = 0
+  autoscale {
+    max_slots = 100
+  }
+}
diff --git a/bigquery_reservation_with_disaster_recovery/motd b/bigquery_reservation_with_disaster_recovery/motd
new file mode 100644
index 00000000..45a906e8
--- /dev/null
+++ b/bigquery_reservation_with_disaster_recovery/motd
@@ -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!
+
+===
diff --git a/bigquery_reservation_with_disaster_recovery/tutorial.md b/bigquery_reservation_with_disaster_recovery/tutorial.md
new file mode 100644
index 00000000..0a3148e6
--- /dev/null
+++ b/bigquery_reservation_with_disaster_recovery/tutorial.md
@@ -0,0 +1,79 @@
+# Bigquery Reservation With Disaster Recovery - Terraform
+
+## Setup
+
+<walkthrough-author name="rileykarson@google.com" analyticsId="UA-125550242-1" tutorialName="bigquery_reservation_with_disaster_recovery" 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
+```