safeguards-plugin icon indicating copy to clipboard operation
safeguards-plugin copied to clipboard

Serverless Framework Plugin to enforce safeguard policies

Results 7 safeguards-plugin issues
Sort by recently updated
recently updated
newest added

If one enables [tracing](https://www.serverless.com/framework/docs/providers/aws/guide/functions/#aws-x-ray-tracing), Serverless generates the following IAM role policy statement with a `*` resource. ```json { "Action": [ "xray:PutTraceSegments", "xray:PutTelemetryRecords" ], "Resource": [ "*" ], "Effect": "Allow" }...

bug
good first issue
help wanted

if `serverless.yaml` file has no defined functions it will fail with the following exception: ``` Error: TypeError: Cannot convert undefined or null to object at Function.entries () at resolveArgsSchema (/Users/gidonk/repos/ciq/ciq-front/ciq-sites/node_modules/serverless/lib/cli/resolve-input.js:13:45)...

Hi, I've written an asynchronous policy that returns a promise and it works, but I'm wondering whether I've implemented it correctly because `serverless deploy` seems to continue running while the...

bug
good first issue
help wanted

AFAIK, safeguards currently execute right at the end, before service is updated remotely. This is painful if there are time consuming operations happening before that. E.g. serverless-webpack. You'll wait a...

enhancement

First cut at resolving #11 Supports the following: * `file:///path/to/policy/file` * `http://host.com/a/b/c` * `https://host.com/a/b/c` * `path/to/file` * `/absolute/path/to/file` The first three are handled by checking that it is a valid...

Speaking with @deitch about this, we have a use-case where we would like to reference and include policy files from within the `serverless.yml` file. These policy files would be located...

enhancement

Hi, this is related to an issue I open on [serverless/serverless/issues/8076](https://github.com/serverless/serverless/issues/8076#issuecomment-675928899). It's seem that safeguards doesn't accept the Framework policy generate for the deployment bucker event if it did forbid...

bug
good first issue
help wanted