Skip to content

Commit dc73920

Browse files
Migrate google_eventarc_trigger resource from DCL to MMv1 (#12832) (#910)
[upstream:80eaa7b5dd063e9975f9b70af355367990f83420] Signed-off-by: Modular Magician <[email protected]>
1 parent 4c83557 commit dc73920

File tree

8 files changed

+309
-0
lines changed

8 files changed

+309
-0
lines changed
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
# This file has some scaffolding to make sure that names are unique and that
2+
# a region and zone are selected when you try to create your Terraform resources.
3+
4+
locals {
5+
name_suffix = "${random_pet.suffix.id}"
6+
}
7+
8+
resource "random_pet" "suffix" {
9+
length = 2
10+
}
11+
12+
provider "google" {
13+
region = "us-central1"
14+
zone = "us-central1-c"
15+
}
Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
resource "google_eventarc_trigger" "primary" {
2+
name = "some-trigger-${local.name_suffix}"
3+
location = "us-central1"
4+
matching_criteria {
5+
attribute = "type"
6+
value = "google.cloud.pubsub.topic.v1.messagePublished"
7+
}
8+
destination {
9+
cloud_run_service {
10+
service = google_cloud_run_service.default.name
11+
region = "us-central1"
12+
}
13+
}
14+
labels = {
15+
foo = "bar"
16+
}
17+
transport {
18+
pubsub {
19+
topic = google_pubsub_topic.foo.id
20+
}
21+
}
22+
}
23+
24+
resource "google_pubsub_topic" "foo" {
25+
name = "some-topic-${local.name_suffix}"
26+
}
27+
28+
resource "google_cloud_run_service" "default" {
29+
name = "some-service-${local.name_suffix}"
30+
location = "us-central1"
31+
32+
template {
33+
spec {
34+
containers {
35+
image = "gcr.io/cloudrun/hello"
36+
ports {
37+
container_port = 8080
38+
}
39+
}
40+
container_concurrency = 50
41+
timeout_seconds = 100
42+
}
43+
}
44+
45+
traffic {
46+
percent = 100
47+
latest_revision = true
48+
}
49+
}
Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
===
2+
3+
These examples use real resources that will be billed to the
4+
Google Cloud Platform project you use - so make sure that you
5+
run "terraform destroy" before quitting!
6+
7+
===
Lines changed: 79 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,79 @@
1+
# Eventarc Trigger With Cloud Run Destination - Terraform
2+
3+
## Setup
4+
5+
<walkthrough-author name="[email protected]" analyticsId="UA-125550242-1" tutorialName="eventarc_trigger_with_cloud_run_destination" repositoryUrl="https://github.com/terraform-google-modules/docs-examples"></walkthrough-author>
6+
7+
Welcome to Terraform in Google Cloud Shell! We need you to let us know what project you'd like to use with Terraform.
8+
9+
<walkthrough-project-billing-setup></walkthrough-project-billing-setup>
10+
11+
Terraform provisions real GCP resources, so anything you create in this session will be billed against this project.
12+
13+
## Terraforming!
14+
15+
Let's use {{project-id}} with Terraform! Click the Cloud Shell icon below to copy the command
16+
to your shell, and then run it from the shell by pressing Enter/Return. Terraform will pick up
17+
the project name from the environment variable.
18+
19+
```bash
20+
export GOOGLE_CLOUD_PROJECT={{project-id}}
21+
```
22+
23+
After that, let's get Terraform started. Run the following to pull in the providers.
24+
25+
```bash
26+
terraform init
27+
```
28+
29+
With the providers downloaded and a project set, you're ready to use Terraform. Go ahead!
30+
31+
```bash
32+
terraform apply
33+
```
34+
35+
Terraform will show you what it plans to do, and prompt you to accept. Type "yes" to accept the plan.
36+
37+
```bash
38+
yes
39+
```
40+
41+
42+
## Post-Apply
43+
44+
### Editing your config
45+
46+
Now you've provisioned your resources in GCP! If you run a "plan", you should see no changes needed.
47+
48+
```bash
49+
terraform plan
50+
```
51+
52+
So let's make a change! Try editing a number, or appending a value to the name in the editor. Then,
53+
run a 'plan' again.
54+
55+
```bash
56+
terraform plan
57+
```
58+
59+
Afterwards you can run an apply, which implicitly does a plan and shows you the intended changes
60+
at the 'yes' prompt.
61+
62+
```bash
63+
terraform apply
64+
```
65+
66+
```bash
67+
yes
68+
```
69+
70+
## Cleanup
71+
72+
Run the following to remove the resources Terraform provisioned:
73+
74+
```bash
75+
terraform destroy
76+
```
77+
```bash
78+
yes
79+
```
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
# This file has some scaffolding to make sure that names are unique and that
2+
# a region and zone are selected when you try to create your Terraform resources.
3+
4+
locals {
5+
name_suffix = "${random_pet.suffix.id}"
6+
}
7+
8+
resource "random_pet" "suffix" {
9+
length = 2
10+
}
11+
12+
provider "google" {
13+
region = "us-central1"
14+
zone = "us-central1-c"
15+
}
Lines changed: 58 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,58 @@
1+
resource "google_eventarc_trigger" "primary" {
2+
name = "some-trigger-${local.name_suffix}"
3+
location = "us-central1"
4+
matching_criteria {
5+
attribute = "type"
6+
value = "google.cloud.eventarc.trigger.v1.created"
7+
}
8+
matching_criteria {
9+
attribute = "trigger"
10+
operator = "match-path-pattern"
11+
value = "trigger-with-wildcard-*"
12+
}
13+
destination {
14+
cloud_run_service {
15+
service = google_cloud_run_service.default.name
16+
region = "us-central1"
17+
}
18+
}
19+
labels = {
20+
foo = "bar"
21+
}
22+
event_data_content_type = "application/protobuf"
23+
service_account = google_service_account.trigger_service_account.email
24+
depends_on = [google_project_iam_member.event_receiver]
25+
}
26+
27+
resource "google_service_account" "trigger_service_account" {
28+
account_id = "trigger-sa-${local.name_suffix}"
29+
}
30+
31+
resource "google_project_iam_member" "event_receiver" {
32+
project = google_service_account.trigger_service_account.project
33+
role = "roles/eventarc.eventReceiver"
34+
member = "serviceAccount:${google_service_account.trigger_service_account.email}"
35+
}
36+
37+
resource "google_cloud_run_service" "default" {
38+
name = "some-service-${local.name_suffix}"
39+
location = "us-central1"
40+
41+
template {
42+
spec {
43+
containers {
44+
image = "gcr.io/cloudrun/hello"
45+
ports {
46+
container_port = 8080
47+
}
48+
}
49+
container_concurrency = 50
50+
timeout_seconds = 100
51+
}
52+
}
53+
54+
traffic {
55+
percent = 100
56+
latest_revision = true
57+
}
58+
}
Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
===
2+
3+
These examples use real resources that will be billed to the
4+
Google Cloud Platform project you use - so make sure that you
5+
run "terraform destroy" before quitting!
6+
7+
===
Lines changed: 79 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,79 @@
1+
# Eventarc Trigger With Path Pattern Filter - Terraform
2+
3+
## Setup
4+
5+
<walkthrough-author name="[email protected]" analyticsId="UA-125550242-1" tutorialName="eventarc_trigger_with_path_pattern_filter" repositoryUrl="https://github.com/terraform-google-modules/docs-examples"></walkthrough-author>
6+
7+
Welcome to Terraform in Google Cloud Shell! We need you to let us know what project you'd like to use with Terraform.
8+
9+
<walkthrough-project-billing-setup></walkthrough-project-billing-setup>
10+
11+
Terraform provisions real GCP resources, so anything you create in this session will be billed against this project.
12+
13+
## Terraforming!
14+
15+
Let's use {{project-id}} with Terraform! Click the Cloud Shell icon below to copy the command
16+
to your shell, and then run it from the shell by pressing Enter/Return. Terraform will pick up
17+
the project name from the environment variable.
18+
19+
```bash
20+
export GOOGLE_CLOUD_PROJECT={{project-id}}
21+
```
22+
23+
After that, let's get Terraform started. Run the following to pull in the providers.
24+
25+
```bash
26+
terraform init
27+
```
28+
29+
With the providers downloaded and a project set, you're ready to use Terraform. Go ahead!
30+
31+
```bash
32+
terraform apply
33+
```
34+
35+
Terraform will show you what it plans to do, and prompt you to accept. Type "yes" to accept the plan.
36+
37+
```bash
38+
yes
39+
```
40+
41+
42+
## Post-Apply
43+
44+
### Editing your config
45+
46+
Now you've provisioned your resources in GCP! If you run a "plan", you should see no changes needed.
47+
48+
```bash
49+
terraform plan
50+
```
51+
52+
So let's make a change! Try editing a number, or appending a value to the name in the editor. Then,
53+
run a 'plan' again.
54+
55+
```bash
56+
terraform plan
57+
```
58+
59+
Afterwards you can run an apply, which implicitly does a plan and shows you the intended changes
60+
at the 'yes' prompt.
61+
62+
```bash
63+
terraform apply
64+
```
65+
66+
```bash
67+
yes
68+
```
69+
70+
## Cleanup
71+
72+
Run the following to remove the resources Terraform provisioned:
73+
74+
```bash
75+
terraform destroy
76+
```
77+
```bash
78+
yes
79+
```

0 commit comments

Comments
 (0)