update_integration_response
async
¶
update_integration_response(
api_id: __string,
integration_id: __string,
integration_response_id: __string,
*,
config_overrides: Optional[AsyncApiGatewayV2ClientConfig] = 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/async_api_gateway_v2.py
6108 6109 6110 6111 6112 6113 6114 6115 6116 6117 6118 6119 6120 6121 6122 6123 6124 6125 6126 6127 6128 6129 6130 6131 6132 6133 6134 6135 6136 6137 6138 6139 6140 6141 6142 6143 6144 6145 6146 6147 6148 6149 6150 6151 6152 6153 6154 6155 6156 6157 6158 6159 6160 6161 6162 6163 6164 6165 6166 6167 6168 6169 6170 6171 6172 6173 6174 6175 6176 6177 6178 6179 6180 6181 6182 6183 6184 6185 6186 6187 6188 6189 6190 6191 | |