serverless-secrets
serverless-secrets copied to clipboard
trek10inc
An opinionated tool for safely managing and deploying Serverless projects and their secrets.
Bumps [lodash](https://github.com/lodash/lodash) from 4.17.4 to 4.17.21. Commits f299b52 Bump to v4.17.21 c4847eb Improve performance of toNumber, trim and trimEnd on large input strings 3469357 Prevent command injection through _.template's variable...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
... when no environment variables are defined in the provider section. ```bash Operating System: win32 Node Version: 12.18.0 Framework Version: 1.72.0 Plugin Version: 3.6.13 SDK Version: 2.3.1 Components Version: 2.30.14...
This is to address network connectivity issue when communicating with AWS when working behind corporate proxy.
This makes it possible to disable the plugin in the `serverless.yml`. The default behaviour should be unchanged.
Closes #34 Cf https://github.com/serverless-heaven/serverless-webpack/issues/387
If your AWS account has many secrets in SSM, the validate secrets procedure will fail with a Throttled Exception from AWS; this is because the AWS provider is calling `ssm.describeParameters`...
If not set it automatically uses the environment variable or defaults set via the serverless region setting.
Giving the following serverless configuration ```yml function1: handler: file1.handler environmentSecrets: ENV1: '/my-project/${opt:stage}/ENV1' function2: handler: file2.handler environmentSecrets: ENV2: '/my-project/${opt:stage}/ENV2' ``` When invoking `function1` the environment is injected with `ENV2` variable instead...
Fixes issues reported in https://github.com/trek10inc/serverless-secrets/issues/31. #What is changed 1. function level secrets have function name as key in .serverless-secrets.json 2. serverless resolves variables after loading the plugins. This is causing...
