-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: optionally set warmer roleName if using default role #321
feat: optionally set warmer roleName if using default role #321
Conversation
@juanjoDiaz Please let me know if I left out any contribution steps or if there are any test cases you feel need to be added. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the very complete PR.
It's much appreciate when a PR describes well the reasoning behind it and it follows the style, includes tests and a good commit description 🙂
Just a couple of minor changes in the docs requested
It seems that coverage is going down. Can you check |
Seems as though serverless-plugin-warmup/src/warmer.js Lines 28 to 40 in c9c3437
Any thoughts? |
Nice, I just ran into this issue too. |
Sorry for the delay. Just a small issue captured by test coverage. |
Optionally set a roleName for the warmers.
Use Case:
Sometimes the default generated Role name exceeds the IAM max name length of 64 characters.
This causes deployments to fail for some users if they do not disable the warmers for deployments.
Example:
Cause:
serverless-plugin-warmup/src/warmer.js
Lines 25 to 40 in 847b45c
Fix:
Optionally provide warmer RoleName field for two main reasons:
Please let me know if I have missed anything... Thanks!