Skip to content

refactor(cdk): Make targetGroupWeights optional - #17009

Open
akash1810 wants to merge 1 commit into
mainfrom
aa/target-group-weight-refactor
Open

akash1810 wants to merge 1 commit into
mainfrom
aa/target-group-weight-refactor

Conversation

@akash1810

@akash1810 akash1810 commented Oct 23, 2026 •

Copy link
Copy Markdown
Member

What does this change?

We currently have targetGroupWeights configured for tag-page-rendering even though since #16965 the EC2 infrastructure has been removed. This change moves targetGroupWeights out of ecsProps so that it can be optionally set, and therefore remove the weight configuration from tag-page-rendering.

Note, the GuCDK library will throw if:

That is, I don't think we need to add any tests here.

Why?

Terser, more readable, code.

How has this change been tested?

CI passing should suffice; this change is a no-op as demonstrated by the CDK snapshots remaining unchanged.

We currently have `targetGroupWeights` configured for tag-page-rendering even though since #16965 the EC2 infrastructure has been removed.

This change moves `targetGroupWeights` out of `ecsProps` so that it can be optionally set.

NOTE: The GuCDK library will throw if:
- EC2 props and ECS props are provided, but no weighting is provided
- Weighting configures traffic to be routed to a target group scaled to 0
@akash1810
akash1810 requested a review from a team as a code owner October 23, 2026 11:44
@akash1810 akash1810 added the maintenance Departmental tracking: maintenance work, not a fix or a feature label Oct 23, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

maintenance Departmental tracking: maintenance work, not a fix or a feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants