You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix Terraform skill to use latest Google provider version
Add constraint to force using Developer Connect when creating Cloud Build trigger
Fix Terraform skill to use Developer Connect instead of Firebase as GitHub app for DC connection
Copy file name to clipboardExpand all lines: skills/gcp-cicd-terraform/SKILL.md
+59Lines changed: 59 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,6 +30,27 @@ terraform {
30
30
31
31
Note: The GCS bucket must have Object Versioning enabled to allow recovery from accidental state corruption or overlapping writes.
32
32
33
+
### Required Provider Version
34
+
Use the Google Cloud Terraform provider version 7.20.0 or higher. This skill utilizes features (e.g., Developer Connect) introduced in Google Provider v7.20.0.
35
+
36
+
```hcl
37
+
terraform {
38
+
required_version = ">= 1.6.0"
39
+
40
+
required_providers {
41
+
google = {
42
+
source = "hashicorp/google"
43
+
version = ">= 7.20.0"
44
+
}
45
+
}
46
+
}
47
+
```
48
+
49
+
To retrieve the latest version of the Google provider, use the following command:
The Agent must follow this lifecycle for every infrastructure change to ensure idempotency and prevent production outages:
35
56
@@ -88,6 +109,44 @@ To maintain a clean module interface, use the main identifier for singleton reso
88
109
- Private Google Access: Subnets should always have private_ip_google_access = true.
89
110
- Workload Identity: Prefer GKE Workload Identity over static Service Account JSON keys.
90
111
112
+
3. Cloud Build Triggers with Developer Connect
113
+
When using Developer Connect git repository links, use `developer_connect_event_config` — NOT `repository_event_config`. The `repository_event_config` block is for Cloud Build v2 repository connections and will not work with Developer Connect resources. An example block to create a Cloud Build trigger with Developer Connect git repository link is as follows:
When configuring `google_developer_connect_connection`, always set `github_app` to `"DEVELOPER_CONNECT"`. Using `"FIREBASE"` is incorrect and will cause triggers to fail.
0 commit comments