defender-serverless icon indicating copy to clipboard operation
defender-serverless copied to clipboard

Configure a Defender environment via code

Results 15 defender-serverless issues
Sort by recently updated
recently updated
newest added

When trying to use the serverless configuration with typescript, like: [Building a serverless app with TypeScript](https://blog.logrocket.com/building-serverless-app-typescript/) you need the right typescript types to declare the configuration. There are two projects...

Via the GUI it is possible to have Sentinels with only an Autotask trigger. It even lets me save the sentinel without any notification selected. So an empty notification channel...

In the running for my nitpickiest comment ever (and that's saying something 🤣 ) Currently the checkmark for the success state is red. That can send mixed messages. Ideally this...

enhancement

Currently the serverless plugin is basically a one-way road for deploying configurations. Defender configurations are defined in `serverless.yml` that can be easily deployed with the possibility of also rolling things...

enhancement

**Palla:** We should make it possible to connect an autotask in the `serverless.yaml` to a relayer that is not defined in the same template. **Use case:** multiple stacks that depend...

enhancement

If possible we should make validation of cron field more stricter. ``` functions: autotask-example-1: name: 'Hello world from serverless' path: './autotasks/hello-world' relayer: ${self:resources.Resources.relayers.relayer-1} trigger: type: "schedule" cron: "4" ``` This...

enhancement

(Nice to have) When creating specific resources users could find useful to see additional data via logs or outputs section. For example when creating Relayer it would be useful to...

enhancement

Users might be confused with generic named Resource and its connection to the system. We could use something like `AutotaskSecrets` to provide more context.

enhancement

We should be careful about using term `stack` in our documentation as it might be confusing for users. For example when changing `stack` value and making multiple deployments there is...

documentation

![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123) ### Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project. #### Snyk changed the following file(s): - `package.json` - `yarn.lock` #### Note...