Closed andersem closed 8 months ago
Fixes the problem where getApiKeysValues would only allow FIRST_API_KEY in the following config, and not SECOND_API_KEY because it's not an object.
getApiKeysValues
FIRST_API_KEY
SECOND_API_KEY
provider: name: aws apiGateway: apiKeys: - name: FIRST_API_KEY_NAME value: FIRST_API_KEY - SECOND_API_KEY
Strings are supported, according to the serverless (docs)[https://www.serverless.com/framework/docs/providers/aws/guide/serverless.yml#api-gateway-v1-rest-api].
Fixes https://github.com/dherault/serverless-offline/issues/1661
Tested with unit tests with both types of input
I guess there's a use case for API_KEYs that can be empty strings?
+1 support string x-api-keys
thank you @andersem !
Description
Fixes the problem where
getApiKeysValues
would only allowFIRST_API_KEY
in the following config, and notSECOND_API_KEY
because it's not an object.Strings are supported, according to the serverless (docs)[https://www.serverless.com/framework/docs/providers/aws/guide/serverless.yml#api-gateway-v1-rest-api].
Motivation and Context
Fixes https://github.com/dherault/serverless-offline/issues/1661
How Has This Been Tested?
Tested with unit tests with both types of input