Struct aws_sdk_appsync::input::CreateResolverInput

#[non_exhaustive]
pub struct CreateResolverInput {
    pub api_id: Option<String>,
    pub type_name: Option<String>,
    pub field_name: Option<String>,
    pub data_source_name: Option<String>,
    pub request_mapping_template: Option<String>,
    pub response_mapping_template: Option<String>,
    pub kind: Option<ResolverKind>,
    pub pipeline_config: Option<PipelineConfig>,
    pub sync_config: Option<SyncConfig>,
    pub caching_config: Option<CachingConfig>,
    pub max_batch_size: i32,
}

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

api_id: Option<String>

The ID for the GraphQL API for which the resolver is being created.

type_name: Option<String>

The name of the Type.

field_name: Option<String>

The name of the field to attach the resolver to.

data_source_name: Option<String>

The name of the data source for which the resolver is being created.

request_mapping_template: Option<String>

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.

response_mapping_template: Option<String>

The mapping template to use for responses from the data source.

kind: Option<ResolverKind>

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 Function objects in a serial manner. You can use a pipeline resolver to run a GraphQL query against multiple data sources.

pipeline_config: Option<PipelineConfig>

The PipelineConfig.

sync_config: Option<SyncConfig>

The SyncConfig for a resolver attached to a versioned data source.

caching_config: Option<CachingConfig>

The caching configuration for the resolver.

max_batch_size: i32

The maximum batching size for a resolver.

Implementations

impl CreateResolverInput

pub async fn make_operation(
    &self,
    _config: &Config
) -> Result<Operation<CreateResolver, AwsErrorRetryPolicy>, BuildError>

Consumes the builder and constructs an Operation<CreateResolver>

pub fn builder() -> Builder

Creates a new builder-style object to manufacture CreateResolverInput

impl CreateResolverInput

pub fn api_id(&self) -> Option<&str>

The ID for the GraphQL API for which the resolver is being created.

pub fn type_name(&self) -> Option<&str>

The name of the Type.

pub fn field_name(&self) -> Option<&str>

The name of the field to attach the resolver to.

pub fn data_source_name(&self) -> Option<&str>

The name of the data source for which the resolver is being created.

pub fn request_mapping_template(&self) -> Option<&str>

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.

pub fn response_mapping_template(&self) -> Option<&str>

The mapping template to use for responses from the data source.

pub fn kind(&self) -> Option<&ResolverKind>

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 Function objects in a serial manner. You can use a pipeline resolver to run a GraphQL query against multiple data sources.

pub fn pipeline_config(&self) -> Option<&PipelineConfig>

The PipelineConfig.

pub fn sync_config(&self) -> Option<&SyncConfig>

The SyncConfig for a resolver attached to a versioned data source.

pub fn caching_config(&self) -> Option<&CachingConfig>

The caching configuration for the resolver.

pub fn max_batch_size(&self) -> i32

The maximum batching size for a resolver.

Trait Implementations

impl Clone for CreateResolverInput

fn clone(&self) -> CreateResolverInput

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for CreateResolverInput

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl PartialEq<CreateResolverInput> for CreateResolverInput

fn eq(&self, other: &CreateResolverInput) -> bool

This method tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &CreateResolverInput) -> bool

This method tests for !=.

impl StructuralPartialEq for CreateResolverInput