Closed
Description
Summary
Have an action in GitHub workflow (PR, push to master) to calculate the size of the jar files and report it in the PR with the trend (increase/decrease).
Why is this needed?
One of our tenet is "Keep it lean", to avoid adding too many dependencies and having powertools too heavy, causing slower cold starts. Having the information in each PR of the size and the trend would help making the good choices.
Which area does this relate to?
Automation, Governance
Solution
Could not find any Java-related GitHub actions (a lot on Js/Ts), but maybe something more generic exists.
Acknowledgment
- This request meets Lambda Powertools Tenets
- Should this be considered in other Lambda Powertools languages? i.e. Python, TypeScript
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Shipped