There's a warning that states that, in Serverless Framework 3.0, apiKeys, usagePlan and resourcePolicy keys are only going to be available under provider.apiGateway, however, there are some extra fields related to the API that are still leftover in the provider key, e.g apiName and endpointType and 1) there's no warning for them 2) it's not possible for use them inside apiGateway (

Hi,

I wanted to enable binary support on API gateway, but could not find the way to do it via component's inputs.

Is this something that you would consider adding in the future?

If so, I can try to add this feature. It doesn't look too complicated.

Thanks!

Describe the bug

The rewrites configuration also supports an object, but this does not currently work in the default Lambda. https://nextjs.org/docs/api-reference/next.config.js/rewrites

Rewrites are applied after checking the filesystem (pages and /public files) and before dynamic routes by default. This behavior can be changed by instead returning an object instead of an array from t

I'm submitting a...

[x ] Bug report  
[ ] Feature request
[ ] Documentation issue or request

In package

[ ] @ng-toolkit/init
[ ] @ng-toolkit/serverless
[x] @ng-toolkit/universal
[ ] @ng-toolkit/pwa
[ ] @ng-toolkit/f

Hi everyone,

I'm building Saas app model where each client should have their own API_KEY specified expiry dateTime as additional authorization method (AWS Cognito User Pool is used by default authorization).

I can see we have one field API_Key but have no idea how appsync works out on selecting specifically which API_KEY corresponding for each clients.

Another scenario using API_Key as

synk report issue

Description

We are synk (https://snyk.io/) for checking used packages.

Synk is complaining about a security issue for serverless-step-functions.
https://snyk.io/vuln/SNYK-JS-DOTPROP-543489

Additional Data

• Serverless Framework Core Version you're using: 1.64.1
• The Plugin Version you're using: 2.17.1
• Operating System: macOS Majove 10.14

According to the documentation it is possible to disable a default alarm on function level.
That would be useful fur self defined alarms also.

alerts:
   definitions:  
      customAlarm:
        ...
      alarms:
         - customAlarm

functions:
   handlerSpecial:
      alarms:
         - customAlarm:
              enabled: false

This is not possible right now w