Robin Thomas

**Classification** * I have a team and an idea. **Project Idea** * A decentralized web store for Chromium extensions **Team** * Robin Thomas: **Ways to Expand** **Eligible Bounties** * https://gitcoin.co/issue/ArweaveTeam/Bounties/4/3162...

The plugin replaces the environment variables defined under `provide.environment` key in `serverless.yml`. Rather than restricting to this, replace the ones that can be defined like: ``` functions: function1: handler: index.handler...

At the moment, we support only 2 serverless lifecycle hooks: - `before:package:initialize` - `offline:start:init` See whether we can accept a list of lifecycle hooks (besides the 2 above) from the...

Since Node.js v18 shall reach its end-of-life on 18 Oct 2023, update to Node.js v20 after this.

Rather than exposing the secret during the build stage (`sls deploy`), figure out a way whereby the secret shall be exposed only during runtime. Some possible ways: 1. Replace all...

We are using the `custom` property (from `serverless.yml`) here: https://github.com/robin-thomas/serverless-aws-secrets/blob/5ff4bb3bf3ee160038ebbc08a8992fa17a5d5991/src/index.ts#L64 Add schema validation for these properties, like mentioned here: https://www.serverless.com/framework/docs/guides/plugins/custom-configuration

Read through the environment variables and check if an environment variable is supposed to be a secret but it is not. For inspiration, refer: https://github.com/serverless/safeguards-plugin/blob/master/safeguards/policies/no-secret-env-vars.js

Possible cli configuration: * `--serverless-file`: path to the `serverless.yml` file * `--secret-id`: id of the secret to look for in AWS Secrets Manager * `--verbose`: support for verbose logging *...