Skip to content

Commit

Permalink
docs: fix documentation of default role
Browse files Browse the repository at this point in the history
  • Loading branch information
juanjoDiaz committed Feb 18, 2024
1 parent 6ac9002 commit 2fd6e60
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ The options are the same for all the warmers:
* **cleanFolder** Whether to automatically delete the generated code folder. You might want to keep it if you are doing some custom packaging (defaults to `true`)
* **name** Name of the generated warmer lambda (defaults to `${service}-${stage}-warmup-plugin-${warmerName}`)
* **roleName** Name to be applied to the default warmer lambda role. Ignored if a the role setting is used (defaults to `${service.service}-${stage}-${region}-${warmerName.toLowerCase()}-role`)
* **role** Role to apply to the warmer lambda (defaults to the role in the provider)
* **role** Role to apply to the warmer lambda (defaults to a custom role with minimal [permissions](#permissions))
* **tags** Tag to apply to the generated warmer lambda (defaults to the serverless default tags)
* **vpc** The VPC and subnets in which to deploy. Can be any [Serverless VPC configuration](https://serverless.com/framework/docs/providers/aws/guide/functions#vpc-configuration) or be set to `false` in order to deploy the warmup function outside of a VPC (defaults to the vpc in the provider)
* **memorySize** The memory to be assigned to the warmer lambda (defaults to `128`)
Expand Down

0 comments on commit 2fd6e60

Please sign in to comment.