LAMBDA-PROXY in combination with request / response configuration

When using Lambda-Proxy in combination with request / response configuration, the serverless deploy removes these before deployment. Is there another way to specify query parameters and response codes?

Although the Lambda-Proxy approach handles these transparently, it still forms a useful part of the API specification and in the case of the query parameters, these are used in API Gateway to configure caching behaviour, so there is value in having them configured there.


I’m asking myself the exact same question, and i’d like some recommendations on the right way to specify the required/optionnal query parameters in Lambda-Proxy mode.