You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
//! [VPC Lattice]() REST and HTTP API lambda integrations
6
8
//!
7
9
//! This crate abstracts over all of these trigger events using standard [`http`](https://github.com/hyperium/http) types minimizing the mental overhead
8
10
//! of understanding the nuances and variation between trigger details allowing you to focus more on your application while also giving you to the maximum flexibility to
// Explicitly empty, as API gateway v1 will merge "headers" and
159
+
// "multi_value_headers" fields together resulting in duplicate response headers.
160
+
headers:HeaderMap::new(),
161
+
// Today, this implementation doesn't provide any additional fields
162
+
#[cfg(feature = "catch-all-fields")]
163
+
other:Default::default(),
164
+
}),
144
165
#[cfg(feature = "pass_through")]
145
166
RequestOrigin::PassThrough => {
146
167
match body {
@@ -154,9 +175,10 @@ impl LambdaResponse {
154
175
feature = "apigw_rest",
155
176
feature = "apigw_http",
156
177
feature = "alb",
157
-
feature = "apigw_websockets"
178
+
feature = "apigw_websockets",
179
+
feature = "vpc_lattice"
158
180
)))]
159
-
_ => compile_error!("Either feature `apigw_rest`, `apigw_http`, `alb`, or `apigw_websockets` must be enabled for the `lambda-http` crate."),
181
+
_ => compile_error!("Either feature `apigw_rest`, `apigw_http`, `alb`, `apigw_websockets` or `vpc_lattice` must be enabled for the `lambda-http` crate."),
0 commit comments