-
Notifications
You must be signed in to change notification settings - Fork 168
Closed as not planned
Labels
automationThis item relates to automationThis item relates to automationidempotencyThis item relates to the Idempotency UtilityThis item relates to the Idempotency UtilityinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)rejectedThis is something we will not be working on. At least, not in the measurable futureThis is something we will not be working on. At least, not in the measurable future
Milestone
Description
Description of the feature request
Problem statement
Before merging new code into main
we are running a workflow that measures the impact of the changes on the final package size. The new utility should be part of this workflow.
Summary of the feature
This issue tracks the work needed to integrate the new utility as part of the workflow mentioned above. The output report that is generated should then include the idempotency util.
Code examples
N/A
Benefits for you and the wider AWS community
This will help the maintainers to make data driven decisions when it comes to package size.
Describe alternatives you've considered
N/A
Additional context
N/A
Related issues, RFCs
Metadata
Metadata
Assignees
Labels
automationThis item relates to automationThis item relates to automationidempotencyThis item relates to the Idempotency UtilityThis item relates to the Idempotency UtilityinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)rejectedThis is something we will not be working on. At least, not in the measurable futureThis is something we will not be working on. At least, not in the measurable future