fix(ecs-patterns): target group ID changes without setting feature flag

[Abogical]

Issue # (if applicable)

Closes #36149

Reason for this change

The feature flag did not stop the target group ID of the ALB to change if the load balancer was private.

Description of changes

The target group ID will not change if the feature flag is not set and remain as ECS.

Describe any new or updated permissions being added

No new permissions are added.

Description of how you validated changes

Unit test added.

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[aws-cdk-automation]

(This review is outdated)

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[Abogical]

There seems to be a bug with the deployment integ runner, cancelling workflow and deploying locally instead. The workflow will not block the merge.

[Abogical]

Test snapshots deployed successfully on the local machine.

[mergify]

Merge Queue Status

✅ The pull request has been merged

This pull request spent 41 minutes 17 seconds in the queue, including 41 minutes 3 seconds waiting for CI.
The checks were run in-place.

Required conditions to merge

• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • fix(ecs-patterns): target group ID changes without setting feature flag #36199
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • fix(ecs-patterns): target group ID changes without setting feature flag #36199
• any of [🛡 GitHub branch protection]:
  • check-success = validate-pr
  • check-neutral = validate-pr
  • check-skipped = validate-pr
• any of [🛡 GitHub branch protection]:
  • check-success = build
  • check-neutral = build
  • check-skipped = build

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.