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
Adds support for Graceful Updater in Compute Managed Instance Groups. (#5975) (#11640)
* Support new features of IGM.updatePolicy (#4956)
* Add new IGM.UpdatePolicy features - minimal_action=REFRESH and most_disruptive_allowed_action
* Fix documentation of most_disruptive_allowed_action
* Make most_disruptive_allowed_action an Optional field.
* Fix RMIG UpdatePolicy flattening.
* Fix most_disruptive_allowed_action documentation - new field is Optional.
* Fix most_disruptive_allowed_action documentation - and improve testing.
* Fix whitespaces in test.
Co-authored-by: Grzegorz Sancewicz <[email protected]>
* Always send minimal_action and most_disruptive_allowed_action with IGM.UpdatePolicy.
* Make minimal_action optional and send null values instead of empty strings
* Remove unnecesary appending to ForceSendFields array
* Fix documentation for minimal_action - field is no longer required.
* Revert making minimal_action optional.
Co-authored-by: Kamil Hajduczenia <[email protected]>
Signed-off-by: Modular Magician <[email protected]>
Co-authored-by: Kamil Hajduczenia <[email protected]>
compute: added field `update_policy.most_disruptive_allowed_action` to `google_compute_instance_group_manager` and `google_compute_region_instance_group_manager`
3
+
```
4
+
```release-note:enhancement
5
+
compute: added value `REFRESH` to field update_policy.minimal_action` in `google_compute_instance_group_manager` and `google_compute_region_instance_group_manager`
Description: `Minimal action to be taken on an instance. You can specify either RESTART to restart existing instances or REPLACE to delete and create new instances from the target template. If you specify a RESTART, the Updater will attempt to perform that action only. However, if the Updater determines that the minimal action you specify is not enough to perform the update, it might perform a more disruptive action.`,
Description: `Minimal action to be taken on an instance. You can specify either REFRESH to update without stopping instances, RESTART to restart existing instances or REPLACE to delete and create new instances from the target template. If you specify a REFRESH, the Updater will attempt to perform that action only. However, if the Updater determines that the minimal action you specify is not enough to perform the update, it might perform a more disruptive action.`,
Description: `Most disruptive action that is allowed to be taken on an instance. You can specify either NONE to forbid any actions, REFRESH to allow actions that do not need instance restart, RESTART to allow actions that can be applied without instance replacing or REPLACE to allow all possible actions. If the Updater determines that the minimal update action needed is more disruptive than most disruptive allowed action you specify it will not perform the update at all.`,
Description: `Minimal action to be taken on an instance. You can specify either RESTART to restart existing instances or REPLACE to delete and create new instances from the target template. If you specify a RESTART, the Updater will attempt to perform that action only. However, if the Updater determines that the minimal action you specify is not enough to perform the update, it might perform a more disruptive action.`,
Description: `Minimal action to be taken on an instance. You can specify either REFRESH to update without stopping instances, RESTART to restart existing instances or REPLACE to delete and create new instances from the target template. If you specify a REFRESH, the Updater will attempt to perform that action only. However, if the Updater determines that the minimal action you specify is not enough to perform the update, it might perform a more disruptive action.`,
Description: `Most disruptive action that is allowed to be taken on an instance. You can specify either NONE to forbid any actions, REFRESH to allow actions that do not need instance restart, RESTART to allow actions that can be applied without instance replacing or REPLACE to allow all possible actions. If the Updater determines that the minimal update action needed is more disruptive than most disruptive allowed action you specify it will not perform the update at all.`,
Copy file name to clipboardExpand all lines: website/docs/r/compute_instance_group_manager.html.markdown
+10-7
Original file line number
Diff line number
Diff line change
@@ -149,16 +149,19 @@ group. You can specify only one value. Structure is [documented below](#nested_a
149
149
150
150
```hcl
151
151
update_policy {
152
-
type = "PROACTIVE"
153
-
minimal_action = "REPLACE"
154
-
max_surge_percent = 20
155
-
max_unavailable_fixed = 2
156
-
min_ready_sec = 50
157
-
replacement_method = "RECREATE"
152
+
type = "PROACTIVE"
153
+
minimal_action = "REPLACE"
154
+
most_disruptive_allowed_action = "REPLACE"
155
+
max_surge_percent = 20
156
+
max_unavailable_fixed = 2
157
+
min_ready_sec = 50
158
+
replacement_method = "RECREATE"
158
159
}
159
160
```
160
161
161
-
*`minimal_action` - (Required) - Minimal action to be taken on an instance. You can specify either `RESTART` to restart existing instances or `REPLACE` to delete and create new instances from the target template. If you specify a `RESTART`, the Updater will attempt to perform that action only. However, if the Updater determines that the minimal action you specify is not enough to perform the update, it might perform a more disruptive action.
162
+
*`minimal_action` - (Required) - Minimal action to be taken on an instance. You can specify either `REFRESH` to update without stopping instances, `RESTART` to restart existing instances or `REPLACE` to delete and create new instances from the target template. If you specify a `REFRESH`, the Updater will attempt to perform that action only. However, if the Updater determines that the minimal action you specify is not enough to perform the update, it might perform a more disruptive action.
163
+
164
+
*`most_disruptive_allowed_action` - (Optional) - Most disruptive action that is allowed to be taken on an instance. You can specify either NONE to forbid any actions, REFRESH to allow actions that do not need instance restart, RESTART to allow actions that can be applied without instance replacing or REPLACE to allow all possible actions. If the Updater determines that the minimal update action needed is more disruptive than most disruptive allowed action you specify it will not perform the update at all.
162
165
163
166
*`type` - (Required) - The type of update process. You can specify either `PROACTIVE` so that the instance group manager proactively executes actions in order to bring instances to their target versions or `OPPORTUNISTIC` so that no action is proactively executed but the update will be performed as part of other actions (for example, resizes or recreateInstances calls).
Copy file name to clipboardExpand all lines: website/docs/r/compute_region_instance_group_manager.html.markdown
+11-8
Original file line number
Diff line number
Diff line change
@@ -158,17 +158,20 @@ group. You can specify one or more values. For more information, see the [offici
158
158
159
159
```hcl
160
160
update_policy {
161
-
type = "PROACTIVE"
162
-
instance_redistribution_type = "PROACTIVE"
163
-
minimal_action = "REPLACE"
164
-
max_surge_percent = 20
165
-
max_unavailable_fixed = 2
166
-
min_ready_sec = 50
167
-
replacement_method = "RECREATE"
161
+
type = "PROACTIVE"
162
+
instance_redistribution_type = "PROACTIVE"
163
+
minimal_action = "REPLACE"
164
+
most_disruptive_allowed_action = "REPLACE"
165
+
max_surge_percent = 20
166
+
max_unavailable_fixed = 2
167
+
min_ready_sec = 50
168
+
replacement_method = "RECREATE"
168
169
}
169
170
```
170
171
171
-
*`minimal_action` - (Required) - Minimal action to be taken on an instance. You can specify either `RESTART` to restart existing instances or `REPLACE` to delete and create new instances from the target template. If you specify a `RESTART`, the Updater will attempt to perform that action only. However, if the Updater determines that the minimal action you specify is not enough to perform the update, it might perform a more disruptive action.
172
+
*`minimal_action` - (Required) - Minimal action to be taken on an instance. You can specify either `REFRESH` to update without stopping instances, `RESTART` to restart existing instances or `REPLACE` to delete and create new instances from the target template. If you specify a `REFRESH`, the Updater will attempt to perform that action only. However, if the Updater determines that the minimal action you specify is not enough to perform the update, it might perform a more disruptive action.
173
+
174
+
*`most_disruptive_allowed_action` - (Optional) - Most disruptive action that is allowed to be taken on an instance. You can specify either NONE to forbid any actions, REFRESH to allow actions that do not need instance restart, RESTART to allow actions that can be applied without instance replacing or REPLACE to allow all possible actions. If the Updater determines that the minimal update action needed is more disruptive than most disruptive allowed action you specify it will not perform the update at all.
172
175
173
176
*`type` - (Required) - The type of update process. You can specify either `PROACTIVE` so that the instance group manager proactively executes actions in order to bring instances to their target versions or `OPPORTUNISTIC` so that no action is proactively executed but the update will be performed as part of other actions (for example, resizes or recreateInstances calls).
0 commit comments