Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(elasticloadbalancingv2): validate port/protocol are not provided for lambda targets #19043

Merged
merged 2 commits into from Feb 21, 2022
Merged

fix(elasticloadbalancingv2): validate port/protocol are not provided for lambda targets #19043

merged 2 commits into from Feb 21, 2022

Commits on Feb 18, 2022

  1. fix(elasticloadbalancingv2): validate port/protocol are not provided … 

    …for lambda targets

When creating a target group with the targetType = `LAMBDA` you should
not provide the port or protocol. If protocol is provided then
CloudFormation will throw an error message. If you provide the port to
CDK, CDK will figure out and provide the protocol as well.

This PR adds validation and throws an error if either port or protocol
is provided when the target type is Lambda.

fixes #12514
    @corymhall
    corymhall committed Feb 18, 2022
    Copy the full SHA
    1c2bc32 View commit details
    Browse the repository at this point in the history

Commits on Feb 21, 2022

  1. Merge branch 'master' into corymhall/throw-lambda-port

    @mergify
    mergify[bot] committed Feb 21, 2022
    Copy the full SHA
    22b85a1 View commit details
    Browse the repository at this point in the history