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
Copy file name to clipboardExpand all lines: docs/upgrading_to_mig_v13.0.md
+54-5Lines changed: 54 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,20 @@
1
-
# Upgrading to MIG v13.0
1
+
# Upgrading to v13.0
2
2
3
-
The v13.0 release of MIG is a backwards incompatible release. Now the `project_id` is required input variable. Earlier it was set to `null` by default. But the `terraform plan` would fail because `google_compute_zones` data block requires a non-null `project_id`.
3
+
The v13.0 release of MIG and instance_template is a backwards incompatible release.
4
+
5
+
## `modules/mig` and `modules/mig_with_percent`
6
+
7
+
Now the `project_id` is required input variable. Earlier it was set to `null` by default. But the `terraform plan` would fail because `google_compute_zones` data block requires a non-null `project_id`.
4
8
Users might be bypassing this by setting project at provider level and not providing `project_id` for mig module.
5
9
10
+
## `modules/instance_template` and `modules/preemptible_and_regular_instance_templates`
11
+
12
+
* Now the `project_id` and `region` is required input variable. Earlier it was set to `null` by default.
13
+
14
+
6
15
## Migration Instructions
7
16
8
-
### Explicitly provide project_id as input to the MIG module
17
+
### Explicitly provide project_id as input to the MIG modules
9
18
10
19
Users would need to provide project_id explicitly while using v13.0 of mig/mig_with_percent.
0 commit comments