diff --git a/cloudbuild_trigger_service_account/backing_file.tf b/cloudbuild_trigger_service_account/backing_file.tf new file mode 100644 index 00000000..c60b1199 --- /dev/null +++ b/cloudbuild_trigger_service_account/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/cloudbuild_trigger_service_account/main.tf b/cloudbuild_trigger_service_account/main.tf new file mode 100644 index 00000000..7f894d7c --- /dev/null +++ b/cloudbuild_trigger_service_account/main.tf @@ -0,0 +1,27 @@ +resource "google_cloudbuild_trigger" "service-account-trigger" { + trigger_template { + branch_name = "master" + repo_name = "my-repo" + } + + service_account = google_service_account.cloudbuild_service_account.id + filename = "cloudbuild.yaml" + depends_on = [ + google_project_iam_member.act_as, + google_project_iam_member.logs_writer + ] +} + +resource "google_service_account" "cloudbuild_service_account" { + account_id = "my-service-account" +} + +resource "google_project_iam_member" "act_as" { + role = "roles/iam.serviceAccountUser" + member = "serviceAccount:${google_service_account.cloudbuild_service_account.email}" +} + +resource "google_project_iam_member" "logs_writer" { + role = "roles/logging.logWriter" + member = "serviceAccount:${google_service_account.cloudbuild_service_account.email}" +} diff --git a/cloudbuild_trigger_service_account/motd b/cloudbuild_trigger_service_account/motd new file mode 100644 index 00000000..45a906e8 --- /dev/null +++ b/cloudbuild_trigger_service_account/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/cloudbuild_trigger_service_account/tutorial.md b/cloudbuild_trigger_service_account/tutorial.md new file mode 100644 index 00000000..2502499a --- /dev/null +++ b/cloudbuild_trigger_service_account/tutorial.md @@ -0,0 +1,79 @@ +# Cloudbuild Trigger Service Account - Terraform + +## Setup + + + +Welcome to Terraform in Google Cloud Shell! We need you to let us know what project you'd like to use with Terraform. + + + +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 +```