update_integration_response
¶
update_integration_response(
api_id: __string,
integration_id: __string,
integration_response_id: __string,
*,
config_overrides: Optional[ApiGatewayV2ClientConfig] = None,
content_handling_strategy: Optional[ContentHandlingStrategy] = None,
integration_response_key: Optional[SelectionKey] = None,
response_parameters: Optional[IntegrationParameters] = None,
response_templates: Optional[TemplateMap] = None,
template_selection_expression: Optional[SelectionExpression] = None,
) -> UpdateIntegrationResponseResponse
Updates an IntegrationResponses.
Parameters:
-
api_id(__string) –The API identifier.
-
content_handling_strategy(Optional[ContentHandlingStrategy], default:None) –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.
-
integration_id(__string) –The integration ID.
-
integration_response_id(__string) –The integration response ID.
-
integration_response_key(Optional[SelectionKey], default:None) –The integration response key.
-
response_parameters(Optional[IntegrationParameters], default:None) –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.
{name} , where name is a valid and unique header name. The mapped non-static value must match the pattern of integration.response.header.{name} or integration.response.body.{JSON-expression} , where{name} is a valid and unique response header name and{JSON-expression} is a valid JSON expression without the $ prefix. -
response_templates(Optional[TemplateMap], default:None) –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.
-
template_selection_expression(Optional[SelectionExpression], default:None) –The template selection expression for the integration response. Supported only for WebSocket APIs.
Raises:
-
BadRequestException–The request is not valid, for example, the input is incomplete or incorrect. See the accompanying error message for details.
-
ConflictException–The requested operation would cause a conflict with the current state of a service resource associated with the request. Resolve the conflict before retrying this request. See the accompanying error message for details.
-
NotFoundException–The resource specified in the request was not found. See the message field for more information.
-
TooManyRequestsException–A limit has been exceeded. See the accompanying error message for details.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_apigatewayv2/_services/api_gateway_v2.py
6015 6016 6017 6018 6019 6020 6021 6022 6023 6024 6025 6026 6027 6028 6029 6030 6031 6032 6033 6034 6035 6036 6037 6038 6039 6040 6041 6042 6043 6044 6045 6046 6047 6048 6049 6050 6051 6052 6053 6054 6055 6056 6057 6058 6059 6060 6061 6062 6063 6064 6065 6066 6067 6068 6069 6070 6071 6072 6073 6074 6075 6076 6077 6078 6079 6080 6081 6082 6083 6084 6085 6086 6087 6088 6089 6090 6091 6092 6093 6094 6095 6096 6097 | |