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
I have an api where a particular path has GET, DELETE, and PUT methods attached. GET and DELETE are handled via serverless-apigateway-service-proxy, but PUT needs to be run through a regular http event (lambda). CORS is enabled. I found that the PUT request was blocked by cors, and when digging into cloudformation-update-template-stack.json found that:
"ApiGatewayMethodApiXXXVarOptions" was in ApiGatewayDeploymentXXX.DependsOn twice, unlike any other entry
But there was only one ApiGatewayMethodApiXXXVarOptions entry
That entry lacked the PUT option
I believe that both serverless-apigateway-service-proxy and regular serverless are trying to generate the ApiGatewayMethodApiXXXVarOptions entry, and one is essentially overwriting the other.
The text was updated successfully, but these errors were encountered:
I have an api where a particular path has GET, DELETE, and PUT methods attached. GET and DELETE are handled via serverless-apigateway-service-proxy, but PUT needs to be run through a regular http event (lambda). CORS is enabled. I found that the PUT request was blocked by cors, and when digging into cloudformation-update-template-stack.json found that:
I believe that both serverless-apigateway-service-proxy and regular serverless are trying to generate the ApiGatewayMethodApiXXXVarOptions entry, and one is essentially overwriting the other.
The text was updated successfully, but these errors were encountered: