We’re using the lambda proxy approach and we’re unable to deploy with a custom header for the options methods. I’ve tried to set the custom header (X-CUSTOM-Auth) on the serverless.yml, e.g.:
The above doesnt deploy the X-CUSTOM-Auth header to the options method integration response. I have to go manually add it, not ideal and not scaleable with a build process. Anyone else have a way this works??