InstancesUpdateOptions

import type { InstancesUpdateOptions } from "https://googleapis.deno.dev/v1/compute:v1.ts";

Additional options for Compute#instancesUpdate.

interface InstancesUpdateOptions {

minimalAction?:

| "INVALID"

| "NO_EFFECT"

| "REFRESH"

| "RESTART";

mostDisruptiveAllowedAction?:

| "INVALID"

| "NO_EFFECT"

| "REFRESH"

| "RESTART";

requestId?: string;

}

§Properties

minimalAction?: "INVALID" | "NO_EFFECT" | "REFRESH" | "RESTART"

[src]

Specifies the action to take when updating an instance even if the updated properties do not require it. If not specified, then Compute Engine acts based on the minimum action that the updated properties require.

mostDisruptiveAllowedAction?: "INVALID" | "NO_EFFECT" | "REFRESH" | "RESTART"

[src]

Specifies the most disruptive action that can be taken on the instance as part of the update. Compute Engine returns an error if the instance properties require a more disruptive action as part of the instance update. Valid options from lowest to highest are NO_EFFECT, REFRESH, and RESTART.

requestId?: string

[src]

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).