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

ProjectsLocationsServicesConnectorsDeleteOptions

import type { ProjectsLocationsServicesConnectorsDeleteOptions } from "https://googleapis.deno.dev/v1/firebasedataconnect:v1beta.ts";

Additional options for FirebaseDataConnect#projectsLocationsServicesConnectorsDelete.

interface ProjectsLocationsServicesConnectorsDeleteOptions {
allowMissing?: boolean;
etag?: string;
force?: boolean;
requestId?: string;
validateOnly?: boolean;
}

§Properties

§
allowMissing?: boolean
[src]

Optional. If true and the Connector is not found, the request will succeed but no action will be taken on the server.

§
etag?: string
[src]

Optional. The etag of the Connector. If this is provided, it must match the server's etag.

§
force?: boolean
[src]

Optional. If set to true, any child resources (i.e. ConnectorRevisions) will also be deleted. Otherwise, the request will only work if the Connector has no child resources.

§
requestId?: string
[src]

Optional. 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. The server will guarantee that for at least 60 minutes after the first request. 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).

§
validateOnly?: boolean
[src]

Optional. If set, validate the request and preview the Connector, but do not actually delete it.