-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugin resetting API Key Source to HEADER #53
Comments
So I played a bit, and before issuing the
The plugin sends the following config to AWS:
And AWS definitely sets the API Key Source back to
|
QuingKhaos
added a commit
to pixelart/serverless-apigw-binary
that referenced
this issue
May 6, 2019
To clarify this issue, this may happen independently if used in a shared gateway scenario or not. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm using this plugin with an shared API Gateway and it resets the config of API Key Source back to
HEADER
Main
serverless.yml
which defines and exports the root API:Deploying this one sets the API Key Source correctly to
AUTHORIZER
The next service which uses
serverless-apigw-binary
:When I deploy this one, the API Key Source is back to
HEADER
. Other services which share the same API Gateway don't have this behavior. Only with this plugin.The text was updated successfully, but these errors were encountered: