open-index/open-npm huggingface dataset:
npm package: @mridang/serverless-resourcetag-plugin
Description: A plugin for the serverless framework to automatically tag all resources and create a resource group.
Author: Mridang Agarwalla
Latest version: 1.10.0

A plugin for the Serverless framework to automatically add tags to
all the resources in the project.

### Why?

The Serverless Framework does support tagging but tags are only applied
upon creation. Any changes to the changes are not reflected in the stack
resources. This is a rather crippling limitation.

Maintaining tags across all the project resources can be tedious.
To further complicate things, not all AWS resources support tagging.
This project gets around these by dynamically fetching the latest
Cloudformation schema from AWS, introspecting all the resources that
support tagging and then dynamically adding the tags to the
resources.

The plugin also uses Resource Groups to ensure that you can see
all the project resources. For more information, see
https://docs.aws.amazon.com/ARG/latest/userguide/resource-groups.html

> [!NOTE]
> This plugin has only been tested with the AWS provider and will
> not work if you are deploying to other providers e.g. GCP.

## Installation

Install using NPM by using the following command

```sh
npm install --save-dev @mridang/serverless-resourcetag-plugin
```

And then add the plugin to your `serverless.yml` file:

```yaml
plugins:
  - @mridang/serverless-resourcetag-plugin
```

A thorough guide on installing plugins can be found at
https://www.serverless.com/framework/docs-guides-plugins

## Usage

On the provider level, use the `tags` property to add the
necessary tags. This is used by the plugin and applied to all
resources automatically. These tags are automatically applied to
all resources - both ones created by the framework and any other
resources you might have added in the `resources` block.

```
$ sls deploy

Packaging aws-node-project for stage dev (us-east-1)

✔ Service packaged (12s)
```

## Contributing

If you have suggestions for how this app could be improved, or
want to report a bug, open an issue - we'd love all and any
contributions.

## License

Apache License 2.0 © 2024 Mridang Agarwalla
npm package: @mridang/serverless-servestatic-plugin
Description: A plugin for the serverless framework to deploy static assets to S3
Author: Mridang Agarwalla
Latest version: 1.7.0

A plugin for the Serverless framework to deploy the static assets into a separate
deployment bucket.

This ensures that that the lambda isn't invoked for serving assets which in turn
reduces the costs and improves performace.

> [!NOTE]
> This plugin has only been tested with the AWS provider and will
> not work if you are deploying to other providers e.g. GCP.

## Installation

Install using NPM by using the following command

```sh
npm install --save-dev @mridang/serverless-servestatic-plugin
```

And then add the plugin to your `serverless.yml` file:

```yaml
plugins:
  - @mridang/serverless-servestatic-plugin
```

A thorough guide on installing plugins can be found at
https://www.serverless.com/framework/docs-guides-plugins

## Usage

### Configuration

The configuration of the plugin is done by defining a custom `servestatic`
object in your serverless.yml with your specific configuration.

All settings are optional and will be set to reasonable defaults if missing.

See the sections below for detailed descriptions of the settings.

```yaml
custom:
  servestatic:
    include:
      - 'public/**/*' # The list of assets to be included
    exclude:
      - '**/' # The list of assets to be excluded
    public: false # A boolean indicating whether thr S3 bucket is public
```

If `public` is enabled, the assets in the bucket can be served directly from the
bucket. Public acess can be disabled if you intend to front the bucket via
CloudFront.

#### Using CloudFront

When you trigger a deployment, the custom resource will unpack all the assets
that the match the glob patterns into the bucket that will be used for serving
static assets.

```
$ sls deploy

Deploying test-logcls to stage dev (us-east-1)
Compiling with Typescript...
Using local tsconfig.json - tsconfig.json
Typescript compiled.

✔ Service deployed to stack test-logcls-dev (104s)

endpoint: https://sfukfimmof3tinylzdbum77uvdu0xtznt.lambda-url.us-east-1.on.aws/
functions:
  probot: test-logcls-dev-probot (22 MB)

Need a faster logging experience than CloudWatch? Try our Dev Mode in Console: run "serverless dev"
```

## Contributing

If you have suggestions for how this app could be improved, or
want to report a bug, open an issue - we'd love all and any
contributions.

## License

Apache License 2.0 © 2024 Mridang Agarwalla
npm package: @mridang/serverless-shortsha-plugin
Description: A plugin for the serverless framework to inspect the setup via Checkov
Author: Mridang Agarwalla
Latest version: 0.9.0

A plugin for the Serverless framework to create a version alias
for the Lambda function which is named after the current git
SHA.

This makes it easier to deduce the version that is running.

> [!NOTE]
> This plugin has only been tested with the AWS provider and will
> not work if you are deploying to other providers e.g. GCP.

## Installation

Install using NPM by using the following command

```sh
npm install --save-dev @mridang/serverless-shortsha-plugin
```

And then add the plugin to your `serverless.yml` file:

```yaml
plugins:
  - @mridang/serverless-shortsha-plugin
```

A thorough guide on installing plugins can be found at
https://www.serverless.com/framework/docs-guides-plugins

## Usage

There isn't anything specific to be done once the plugin is installed.
When you trigger a deployment, the plugin will take the short SHA
of the current directory (assuming that the project is in fact a
a Git repository).

```
$ sls deploy

Deploying test-logcls to stage dev (us-east-1)
Compiling with Typescript...
Using local tsconfig.json - tsconfig.json
Typescript compiled.

Warning: Package patterns at function level are only applicable if package.individually is set to true at service level or function level in serverless.yaml. The framework will ignore the patterns defined at the function level and apply only the service-wide ones.
Warning: cloudformation scan results:

Alias "40d313f" added for function "ProbotLambdaFunction" in the CloudFormation template

✔ Service deployed to stack test-logcls-dev (104s)

endpoint: https://sfukfimmof3tinylzdbum77uvdu0xtznt.lambda-url.us-east-1.on.aws/
functions:
  probot: test-logcls-dev-probot (22 MB)

Need a faster logging experience than CloudWatch? Try our Dev Mode in Console: run "serverless dev"
```

## Contributing

If you have suggestions for how this app could be improved, or
want to report a bug, open an issue - we'd love all and any
contributions.

## License

Apache License 2.0 © 2024 Mridang Agarwalla