An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
↳ zone
string
The name of the zone for this request.
getNodeGroup
Name of the NodeGroup resource whose nodes will go under maintenance simulation.
Returns
Type
Description
string
setNodeGroup
Name of the NodeGroup resource whose nodes will go under maintenance simulation.
An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
Returns
Type
Description
string
hasRequestId
clearRequestId
setRequestId
An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
Parameter
Name
Description
var
string
Returns
Type
Description
$this
getZone
The name of the zone for this request.
Returns
Type
Description
string
setZone
The name of the zone for this request.
Parameter
Name
Description
var
string
Returns
Type
Description
$this
static::build
Parameters
Name
Description
project
string
Project ID for this request.
zone
string
The name of the zone for this request.
nodeGroup
string
Name of the NodeGroup resource whose nodes will go under maintenance simulation.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[],[],null,["# Compute V1 Client - Class SimulateMaintenanceEventNodeGroupRequest (1.35.0)\n\nVersion latestkeyboard_arrow_down\n\n- [1.35.0 (latest)](/php/docs/reference/cloud-compute/latest/V1.SimulateMaintenanceEventNodeGroupRequest)\n- [1.34.0](/php/docs/reference/cloud-compute/1.34.0/V1.SimulateMaintenanceEventNodeGroupRequest)\n- [1.33.0](/php/docs/reference/cloud-compute/1.33.0/V1.SimulateMaintenanceEventNodeGroupRequest)\n- [1.32.0](/php/docs/reference/cloud-compute/1.32.0/V1.SimulateMaintenanceEventNodeGroupRequest)\n- [1.31.0](/php/docs/reference/cloud-compute/1.31.0/V1.SimulateMaintenanceEventNodeGroupRequest)\n- [1.30.0](/php/docs/reference/cloud-compute/1.30.0/V1.SimulateMaintenanceEventNodeGroupRequest)\n- [1.29.0](/php/docs/reference/cloud-compute/1.29.0/V1.SimulateMaintenanceEventNodeGroupRequest)\n- [1.28.0](/php/docs/reference/cloud-compute/1.28.0/V1.SimulateMaintenanceEventNodeGroupRequest)\n- [1.27.0](/php/docs/reference/cloud-compute/1.27.0/V1.SimulateMaintenanceEventNodeGroupRequest)\n- [1.26.0](/php/docs/reference/cloud-compute/1.26.0/V1.SimulateMaintenanceEventNodeGroupRequest)\n- [1.25.0](/php/docs/reference/cloud-compute/1.25.0/V1.SimulateMaintenanceEventNodeGroupRequest)\n- [1.24.0](/php/docs/reference/cloud-compute/1.24.0/V1.SimulateMaintenanceEventNodeGroupRequest)\n- [1.23.0](/php/docs/reference/cloud-compute/1.23.0/V1.SimulateMaintenanceEventNodeGroupRequest)\n- [1.22.1](/php/docs/reference/cloud-compute/1.22.1/V1.SimulateMaintenanceEventNodeGroupRequest)\n- [1.21.0](/php/docs/reference/cloud-compute/1.21.0/V1.SimulateMaintenanceEventNodeGroupRequest)\n- [1.20.0](/php/docs/reference/cloud-compute/1.20.0/V1.SimulateMaintenanceEventNodeGroupRequest)\n- [1.19.0](/php/docs/reference/cloud-compute/1.19.0/V1.SimulateMaintenanceEventNodeGroupRequest)\n- [1.18.1](/php/docs/reference/cloud-compute/1.18.1/V1.SimulateMaintenanceEventNodeGroupRequest)\n- [1.17.0](/php/docs/reference/cloud-compute/1.17.0/V1.SimulateMaintenanceEventNodeGroupRequest)\n- [1.16.2](/php/docs/reference/cloud-compute/1.16.2/V1.SimulateMaintenanceEventNodeGroupRequest)\n- [1.14.0](/php/docs/reference/cloud-compute/1.14.0/V1.SimulateMaintenanceEventNodeGroupRequest)\n- [1.13.0](/php/docs/reference/cloud-compute/1.13.0/V1.SimulateMaintenanceEventNodeGroupRequest)\n- [1.12.1](/php/docs/reference/cloud-compute/1.12.1/V1.SimulateMaintenanceEventNodeGroupRequest)\n- [1.11.1](/php/docs/reference/cloud-compute/1.11.1/V1.SimulateMaintenanceEventNodeGroupRequest)\n- [1.10.1](/php/docs/reference/cloud-compute/1.10.1/V1.SimulateMaintenanceEventNodeGroupRequest)\n- [1.9.1](/php/docs/reference/cloud-compute/1.9.1/V1.SimulateMaintenanceEventNodeGroupRequest)\n- [1.8.3](/php/docs/reference/cloud-compute/1.8.3/V1.SimulateMaintenanceEventNodeGroupRequest)\n- [1.7.1](/php/docs/reference/cloud-compute/1.7.1/V1.SimulateMaintenanceEventNodeGroupRequest)\n- [1.6.1](/php/docs/reference/cloud-compute/1.6.1/V1.SimulateMaintenanceEventNodeGroupRequest)\n- [1.5.0](/php/docs/reference/cloud-compute/1.5.0/V1.SimulateMaintenanceEventNodeGroupRequest) \nReference documentation and code samples for the Compute V1 Client class SimulateMaintenanceEventNodeGroupRequest.\n\nA request message for NodeGroups.SimulateMaintenanceEvent. See the method description for details.\n\nGenerated from protobuf message `google.cloud.compute.v1.SimulateMaintenanceEventNodeGroupRequest`\n\nNamespace\n---------\n\nGoogle \\\\ Cloud \\\\ Compute \\\\ V1\n\nMethods\n-------\n\n### __construct\n\nConstructor.\n\n### getNodeGroup\n\nName of the NodeGroup resource whose nodes will go under maintenance simulation.\n\n### setNodeGroup\n\nName of the NodeGroup resource whose nodes will go under maintenance simulation.\n\n### getNodeGroupsSimulateMaintenanceEventRequestResource\n\nThe body resource for this request\n\n### hasNodeGroupsSimulateMaintenanceEventRequestResource\n\n### clearNodeGroupsSimulateMaintenanceEventRequestResource\n\n### setNodeGroupsSimulateMaintenanceEventRequestResource\n\nThe body resource for this request\n\n### getProject\n\nProject ID for this request.\n\n### setProject\n\nProject ID for this request.\n\n### getRequestId\n\nAn optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).\n\n### hasRequestId\n\n### clearRequestId\n\n### setRequestId\n\nAn optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).\n\n### getZone\n\nThe name of the zone for this request.\n\n### setZone\n\nThe name of the zone for this request.\n\n### static::build"]]