Struct aws_sdk_apigatewayv2::client::fluent_builders::UpdateIntegrationResponse [−][src]
pub struct UpdateIntegrationResponse<C = DynConnector, M = DefaultMiddleware, R = Standard> { /* fields omitted */ }
Expand description
Fluent builder constructing a request to UpdateIntegrationResponse
.
Updates an IntegrationResponses.
Implementations
impl<C, M, R> UpdateIntegrationResponse<C, M, R> where
C: SmithyConnector,
M: SmithyMiddleware<C>,
R: NewRequestPolicy,
impl<C, M, R> UpdateIntegrationResponse<C, M, R> where
C: SmithyConnector,
M: SmithyMiddleware<C>,
R: NewRequestPolicy,
pub async fn send(
self
) -> Result<UpdateIntegrationResponseOutput, SdkError<UpdateIntegrationResponseError>> where
R::Policy: SmithyRetryPolicy<UpdateIntegrationResponseInputOperationOutputAlias, UpdateIntegrationResponseOutput, UpdateIntegrationResponseError, UpdateIntegrationResponseInputOperationRetryAlias>,
pub async fn send(
self
) -> Result<UpdateIntegrationResponseOutput, SdkError<UpdateIntegrationResponseError>> where
R::Policy: SmithyRetryPolicy<UpdateIntegrationResponseInputOperationOutputAlias, UpdateIntegrationResponseOutput, UpdateIntegrationResponseError, UpdateIntegrationResponseInputOperationRetryAlias>,
Sends the request and returns the response.
If an error occurs, an SdkError
will be returned with additional details that
can be matched against.
By default, any retryable failures will be retried twice. Retry behavior is configurable with the RetryConfig, which can be set when configuring the client.
The API identifier.
Supported only for WebSocket APIs. Specifies how to handle response payload content type conversions. Supported values are CONVERT_TO_BINARY and CONVERT_TO_TEXT, with the following behaviors:
CONVERT_TO_BINARY: Converts a response payload from a Base64-encoded string to the corresponding binary blob.
CONVERT_TO_TEXT: Converts a response payload from a binary blob to a Base64-encoded string.
If this property is not defined, the response payload will be passed through from the integration response to the route response or method response without modification.
Supported only for WebSocket APIs. Specifies how to handle response payload content type conversions. Supported values are CONVERT_TO_BINARY and CONVERT_TO_TEXT, with the following behaviors:
CONVERT_TO_BINARY: Converts a response payload from a Base64-encoded string to the corresponding binary blob.
CONVERT_TO_TEXT: Converts a response payload from a binary blob to a Base64-encoded string.
If this property is not defined, the response payload will be passed through from the integration response to the route response or method response without modification.
The integration ID.
The integration ID.
The integration response ID.
The integration response ID.
The integration response key.
The integration response key.
Adds a key-value pair to ResponseParameters
.
To override the contents of this collection use set_response_parameters
.
A key-value map specifying response parameters that are passed to the method response from the backend. The key is a method response header parameter name and the mapped value is an integration response header value, a static value enclosed within a pair of single quotes, or a JSON expression from the integration response body. The mapping key must match the pattern of method.response.header.
A key-value map specifying response parameters that are passed to the method response from the backend. The key is a method response header parameter name and the mapped value is an integration response header value, a static value enclosed within a pair of single quotes, or a JSON expression from the integration response body. The mapping key must match the pattern of method.response.header.
Adds a key-value pair to ResponseTemplates
.
To override the contents of this collection use set_response_templates
.
The collection of response templates for the integration response as a string-to-string map of key-value pairs. Response templates are represented as a key/value map, with a content-type as the key and a template as the value.
The collection of response templates for the integration response as a string-to-string map of key-value pairs. Response templates are represented as a key/value map, with a content-type as the key and a template as the value.
The template selection expression for the integration response. Supported only for WebSocket APIs.
The template selection expression for the integration response. Supported only for WebSocket APIs.
Trait Implementations
Auto Trait Implementations
impl<C = DynConnector, M = DefaultMiddleware, R = Standard> !RefUnwindSafe for UpdateIntegrationResponse<C, M, R>
impl<C, M, R> Send for UpdateIntegrationResponse<C, M, R> where
C: Send + Sync,
M: Send + Sync,
R: Send + Sync,
impl<C, M, R> Sync for UpdateIntegrationResponse<C, M, R> where
C: Send + Sync,
M: Send + Sync,
R: Send + Sync,
impl<C, M, R> Unpin for UpdateIntegrationResponse<C, M, R>
impl<C = DynConnector, M = DefaultMiddleware, R = Standard> !UnwindSafe for UpdateIntegrationResponse<C, M, R>
Blanket Implementations
Mutably borrows from an owned value. Read more
Attaches the provided Subscriber
to this type, returning a
WithDispatch
wrapper. Read more
Attaches the current default Subscriber
to this type, returning a
WithDispatch
wrapper. Read more