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

GoogleCloudIntegrationsV1alphaIntegrationVersion

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

The integration version definition.

interface GoogleCloudIntegrationsV1alphaIntegrationVersion {
createdFromTemplate?: string;
readonly createTime?: Date;
databasePersistencePolicy?: "DATABASE_PERSISTENCE_POLICY_UNSPECIFIED" | "DATABASE_PERSISTENCE_DISABLED" | "DATABASE_PERSISTENCE_ASYNC";
description?: string;
enableVariableMasking?: boolean;
lastModifierEmail?: string;
lockHolder?: string;
readonly name?: string;
origin?:
| "UNSPECIFIED"
| "UI"
| "PIPER_V2"
| "PIPER_V3"
| "APPLICATION_IP_PROVISIONING"
| "TEST_CASE";
parentTemplateId?: string;
runAsServiceAccount?: string;
snapshotNumber?: bigint;
readonly state?:
| "INTEGRATION_STATE_UNSPECIFIED"
| "DRAFT"
| "ACTIVE"
| "ARCHIVED"
| "SNAPSHOT";
readonly status?:
| "UNKNOWN"
| "DRAFT"
| "ACTIVE"
| "ARCHIVED"
| "SNAPSHOT";
readonly updateTime?: Date;
userLabel?: string;
}

§Properties

§

Optional. Cloud Logging details for the integration version

§
createdFromTemplate?: string
[src]

Optional. Optional. The resource name of the template from which the integration is created.

§
readonly createTime?: Date
[src]

Output only. Auto-generated.

§
databasePersistencePolicy?: "DATABASE_PERSISTENCE_POLICY_UNSPECIFIED" | "DATABASE_PERSISTENCE_DISABLED" | "DATABASE_PERSISTENCE_ASYNC"
[src]

Optional. Flag to disable database persistence for execution data, including event execution info, execution export info, execution metadata index and execution param index.

§
description?: string
[src]

Optional. The integration description.

§
enableVariableMasking?: boolean
[src]

Optional. True if variable masking feature should be turned on for this version

§

Optional. Error Catch Task configuration for the integration. It's optional.

§

Optional. Config Parameters that are expected to be passed to the integration when an integration is published. This consists of all the parameters that are expected to provide configuration in the integration execution. This gives the user the ability to provide default values, value, add information like connection url, project based configuration value and also provide data types of each parameter.

§

Optional. Parameters that are expected to be passed to the integration when an event is triggered. This consists of all the parameters that are expected in the integration execution. This gives the user the ability to provide default values, add information like PII and also provide data types of each parameter.

§

Optional. Parameters that are expected to be passed to the integration when an event is triggered. This consists of all the parameters that are expected in the integration execution. This gives the user the ability to provide default values, add information like PII and also provide data types of each parameter.

§
lastModifierEmail?: string
[src]

Optional. The last modifier's email address. Generated based on the End User Credentials/LOAS role of the user making the call.

§
lockHolder?: string
[src]

Optional. The edit lock holder's email address. Generated based on the End User Credentials/LOAS role of the user making the call.

§
readonly name?: string
[src]

Output only. Auto-generated primary key.

§
origin?: "UNSPECIFIED" | "UI" | "PIPER_V2" | "PIPER_V3" | "APPLICATION_IP_PROVISIONING" | "TEST_CASE"
[src]

Optional. The origin that indicates where this integration is coming from.

§
parentTemplateId?: string
[src]

Optional. The id of the template which was used to create this integration_version.

§
runAsServiceAccount?: string
[src]

Optional. The run-as service account email, if set and auth config is not configured, that will be used to generate auth token to be used in Connector task, Rest caller task and Cloud function task.

§
snapshotNumber?: bigint
[src]

Optional. An increasing sequence that is set when a new snapshot is created. The last created snapshot can be identified by [workflow_name, org_id latest(snapshot_number)]. However, last created snapshot need not be same as the HEAD. So users should always use "HEAD" tag to identify the head.

§
readonly state?: "INTEGRATION_STATE_UNSPECIFIED" | "DRAFT" | "ACTIVE" | "ARCHIVED" | "SNAPSHOT"
[src]

Output only. User should not set it as an input.

§
readonly status?: "UNKNOWN" | "DRAFT" | "ACTIVE" | "ARCHIVED" | "SNAPSHOT"
[src]

Output only. Generated by eventbus. User should not set it as an input.

§

Optional. Task configuration for the integration. It's optional, but the integration doesn't do anything without task_configs.

§

Optional. Task configuration for the integration. It's optional, but the integration doesn't do anything without task_configs.

§

Optional. Contains a graph of tasks that will be executed before putting the event in a terminal state (SUCCEEDED/FAILED/FATAL), regardless of success or failure, similar to "finally" in code.

§

Optional. Trigger configurations.

§

Optional. Trigger configurations.

§
readonly updateTime?: Date
[src]

Output only. Auto-generated.

§
userLabel?: string
[src]

Optional. A user-defined label that annotates an integration version. Typically, this is only set when the integration version is created.