feat(elasticloadbalancingv2): support AdvertiseTrustStoreCaNames for mTLS

[kdnakt]

Issue # (if applicable)

N/A

Reason for this change

AWS Application Load Balancer introduces Certificate Authority advertisement to simplify client behavior while using Mutual TLS

Ref: MutualAuthenticationAttributes

Description of changes

Added advertiseTrustStoreCaNames property for MutualAuthentication.

Description of how you validated changes

Updated alb/listener.test.ts and integ.alb-mtls.ts.

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 80.84%. Comparing base (4327ed0) to head (53acc65).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #32678   +/-   ##
=======================================
  Coverage   80.84%   80.84%           
=======================================
  Files         236      236           
  Lines       14230    14230           
  Branches     2487     2487           
=======================================
  Hits        11504    11504           
  Misses       2442     2442           
  Partials      284      284           

Flag	Coverage Δ
suite.unit	80.84% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
packages/aws-cdk	79.64% <ø> (ø)
packages/aws-cdk-lib/core	82.14% <ø> (ø)

[lpizzinidev]

What about changing the type to a boolean and removing the enum? It would provide a cleaner interface

[kdnakt]

Okay I will try it

[lpizzinidev]

Thanks 👍 You can find a sample for the suggested approach here

[kdnakt]

Thank you for the nice sample! I made an update according to it.

[lpizzinidev]

Nice 👍

[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).

[gracelu0]

Hi @kdnakt , looks like there is a merge conflict that needs to be resolved before this can be merged. Let us know if you have any issues resolving it. Thanks!

[kdnakt]

Thanks for letting me know. I'll try to resolve the conflict!

Pull request has been modified.

[aaythapa]

@mergify update

[mergify]

update

❌ Mergify doesn't have permission to update

For security reasons, Mergify can't update this pull request. Try updating locally.
GitHub response: refusing to allow a GitHub App to create or update workflow .github/workflows/analytics-metadata-updater.yml without workflows permission

[aaythapa]

@mergify update

[mergify]

update

❌ Mergify doesn't have permission to update

For security reasons, Mergify can't update this pull request. Try updating locally.
GitHub response: refusing to allow a GitHub App to create or update workflow .github/workflows/analytics-metadata-updater.yml without workflows permission

[aaythapa]

@mergify update

[mergify]

update

☑️ Nothing to do

• #commits-behind > 0 [📌 update requirement]
• -closed [📌 update requirement]
• -conflict [📌 update requirement]
• queue-position = -1 [📌 update requirement]

[aaythapa]

Thank you for contributing

[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).

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: 53acc65
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[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.