CreateResolverRequest
import type { CreateResolverRequest } from "https://aws-api.deno.dev/v0.3/services/appsync.ts?docs=full";interface CreateResolverRequest {
apiId: string;
cachingConfig?: CachingConfig | null;
dataSourceName?: string | null;
fieldName: string;
kind?: ResolverKind | null;
maxBatchSize?: number | null;
pipelineConfig?: PipelineConfig | null;
requestMappingTemplate?: string | null;
responseMappingTemplate?: string | null;
syncConfig?: SyncConfig | null;
typeName: string;
}§Properties
§
cachingConfig?: CachingConfig | null
[src]The caching configuration for the resolver.
§
dataSourceName?: string | null
[src]The name of the data source for which the resolver is being created.
§
kind?: ResolverKind | null
[src]The resolver type.
- UNIT: A UNIT resolver type. A UNIT resolver is the default resolver type. You can use a UNIT resolver to run a GraphQL query against a single data source.
- PIPELINE: A PIPELINE resolver type.
You can use a PIPELINE resolver to invoke a series of
Functionobjects in a serial manner. You can use a pipeline resolver to run a GraphQL query against multiple data sources.
§
pipelineConfig?: PipelineConfig | null
[src]The PipelineConfig.
§
requestMappingTemplate?: string | null
[src]The mapping template to use for requests.
A resolver uses a request mapping template to convert a GraphQL expression into a format that a data source can understand. Mapping templates are written in Apache Velocity Template Language (VTL).
VTL request mapping templates are optional when using an Lambda data source. For all other data sources, VTL request and response mapping templates are required.
§
responseMappingTemplate?: string | null
[src]The mapping template to use for responses from the data source.
§
syncConfig?: SyncConfig | null
[src]The SyncConfig for a resolver attached to a versioned data source.