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

ProjectsLocationsIntegrationsExecutionsListOptions

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

Additional options for Integrations#projectsLocationsIntegrationsExecutionsList.

interface ProjectsLocationsIntegrationsExecutionsListOptions {
filter?: string;
[filterParams.customFilter]?: string;
[filterParams.endTime]?: bigint;
[filterParams.eventStatuses]?: string;
[filterParams.executionId]?: string;
[filterParams.parameterKey]?: string;
[filterParams.parameterPairKey]?: string;
[filterParams.parameterPairValue]?: string;
[filterParams.parameterType]?: string;
[filterParams.parameterValue]?: string;
[filterParams.startTime]?: bigint;
[filterParams.taskStatuses]?: string;
[filterParams.workflowName]?: string;
orderBy?: string;
pageSize?: number;
pageToken?: string;
readMask?: string;
refreshAcl?: boolean;
snapshotMetadataWithoutParams?: boolean;
truncateParams?: boolean;
}

§Properties

§
filter?: string
[src]

Optional. Standard filter field, we support filtering on following fields: workflow_name: the name of the integration. CreateTimestamp: the execution created time. event_execution_state: the state of the executions. execution_id: the id of the execution. trigger_id: the id of the trigger. parameter_type: the type of the parameters involved in the execution. All fields support for EQUALS, in additional: CreateTimestamp support for LESS_THAN, GREATER_THAN ParameterType support for HAS For example: "parameter_type" HAS "string" Also supports operators like AND, OR, NOT For example, trigger_id="id1" AND workflow_name="testWorkflow"

§
[filterParams.customFilter]?: string
[src]

Optional user-provided custom filter.

§
[filterParams.endTime]?: bigint
[src]

End timestamp.

§
[filterParams.eventStatuses]?: string
[src]

List of possible event statuses.

§
[filterParams.executionId]?: string
[src]

Execution id.

§
[filterParams.parameterKey]?: string
[src]

Param key. DEPRECATED. User parameter_pair_key instead.

§
[filterParams.parameterPairKey]?: string
[src]

Param key in the key value pair filter.

§
[filterParams.parameterPairValue]?: string
[src]

Param value in the key value pair filter.

§
[filterParams.parameterType]?: string
[src]

Param type.

§
[filterParams.parameterValue]?: string
[src]

Param value. DEPRECATED. User parameter_pair_value instead.

§
[filterParams.startTime]?: bigint
[src]

Start timestamp.

§
[filterParams.taskStatuses]?: string
[src]

List of possible task statuses.

§
[filterParams.workflowName]?: string
[src]

Workflow name.

§
orderBy?: string
[src]

Optional. The results would be returned in order you specified here. Currently supporting "last_modified_time" and "create_time".

§
pageSize?: number
[src]

Optional. The size of entries in the response.

§
pageToken?: string
[src]

Optional. The token returned in the previous response.

§
readMask?: string
[src]

Optional. View mask for the response data. If set, only the field specified will be returned as part of the result. If not set, all fields in event execution info will be filled and returned.

§
refreshAcl?: boolean
[src]

Optional. If true, the service will use the most recent acl information to list event execution infos and renew the acl cache. Note that fetching the most recent acl is synchronous, so it will increase RPC call latency.

§
snapshotMetadataWithoutParams?: boolean
[src]

Optional. If true, the service will provide execution info with snapshot metadata only i.e. without event parameters.

§
truncateParams?: boolean
[src]

Optional. If true, the service will truncate the params to only keep the first 1000 characters of string params and empty the executions in order to make response smaller. Only works for UI and when the params fields are not filtered out.