apiKeys with declared specific name and value are not utilized

[bitsofinfo]

serverless: 2.69.1
serverless-offline: 8.3.1

I have this declared:

  # api keys (values must be at least 20chars long)
  apiGateway:
    apiKeys:
      - name: ${self:service.name}-${opt:stage, 'dev'}-apiKey
         value: ${ssm:/aws/reference/secretsmanager/myapp/dev/apiKey}

I have a http event based function that is flagged as private: true

I start serverless-offline:

No matter what I am forced to use some generated key

...
offline: Starting Offline: local us-west-2.
offline: Key with token: d41d8cd98f00b204e9800998ecf8427e
offline: Remember to use x-api-key on the request headers
...

This syntax is valid in the serverless docs https://www.serverless.com/framework/docs/providers/aws/events/apigateway#setting-api-keys-for-your-rest-api

[bitsofinfo]

#963

[medikoo]

@bitsofinfo thanks for report. PR with a fix is welcome

[bitsofinfo]

not sure why this was closed, definately an issue

[dnalborczyk]

@bitsofinfo I want to tackle this issue next. it looks like the flag (option) for setting an apiKey is really not needed, as it can be done with the serverless config itself (as your example is outlining above). it is possible that the apikeys key/value pair in the provider.apiGateway section was not introduced yet in serverless when support was implemented in serverless-offline.