Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

ProjectsLocationsBareMetalClustersBareMetalNodePoolsDeleteOptions

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

Additional options for gkeonprem#projectsLocationsBareMetalClustersBareMetalNodePoolsDelete.

interface ProjectsLocationsBareMetalClustersBareMetalNodePoolsDeleteOptions {
allowMissing?: boolean;
etag?: string;
ignoreErrors?: boolean;
validateOnly?: boolean;
}

§Properties

§
allowMissing?: boolean
[src]

If set to true, and the bare metal node pool is not found, the request will succeed but no action will be taken on the server and return a completed LRO.

§
etag?: string
[src]

The current etag of the BareMetalNodePool. If an etag is provided and does not match the current etag of the node pool, deletion will be blocked and an ABORTED error will be returned.

§
ignoreErrors?: boolean
[src]

If set to true, the deletion of a bare metal node pool resource will succeed even if errors occur during deletion. This parameter can be used when you want to delete GCP's node pool resource and you've already deleted the on-prem admin cluster that hosted your node pool. WARNING: Using this parameter when your user cluster still exists may result in a deleted GCP node pool but an existing on-prem node pool.

§
validateOnly?: boolean
[src]

If set, only validate the request, but do not actually delete the node pool.