This is:

• Bug

Detailed Description

When API key is loaded from DB, its permissions are loaded together with the API key data. Once that API key is authenticated, and authorization kicks in, it stores the initial permissions into a cache object, which lives as long as Lambda is alive.

This introduces a problem when we update API key permissions. On subsequent requests, even though th

Is your feature request related to a problem? Please describe.
Yarn packages aren't being cached on e2e tests and build workflows

Describe the solution you'd like
Add caching for npm packages and Cypress (except @sls-next packages) so that workflows will be faster to run

Describe alternatives you've considered
N/A, it will help improve CI workflow speed

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!

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

Right now settings are just passed in through the settings file. This is somewhat limiting if there is a value that will be dynamic with deployments (such as a docker image file, etc.) We should support accepting settings through environment variables, the CLI, the current settings file, and any mix of those.

The order of precedence with mixed should be CLI -> environment -> config file.

If

This is a Bug Report

Description

When