-
Notifications
You must be signed in to change notification settings - Fork 4k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
refactor(elbv2): make load balancer targets bind to interfaces (#4132)
The `attachToApplicationTargetGroup()` (and similar for the NLB) methods of the load balancer target interfaces took a concrete TargetGroup class. This deviates from established CDK standards, and prevents their use with imported TargetGroups. Bring the code in line with expectations. Fixes #4121.
- Loading branch information
Showing
8 changed files
with
41 additions
and
20 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1180c1b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rix0rrr ,
Sorry to call you out directly, but changes in at least this commit are directly hindering a deployment for us. At the very least, the error I'm encountering is from this commit. I've tried Stackoverflow, searching gitter history, reading aws docs, and actually trying stuff in the aws console. I have not found something that will help me with regards to formulating my infrastructure differently in aws-cdk. From what I can tell, what I'm trying is possible. I have live servers with the setup running right now.
This is getting triggered on
cdk diff
andcdk deploy
:1180c1b#diff-2db67fa7f5c77699be5c76d95371fcd5R550
It appears there is now a restriction on adding AutoScalingGroups to multiple Target Groups. I have had code that has been working fine since 0.8.0 and has not been modified (except for breaking changes). After upgrading beyond 1.13.0 I'm now encountering problems with no clear resolution available.
I need to have multiple Load Balancers(ALB's) point to the same ASG. Something must have changed with how Target groups are constructed in these later versions.
The reason for this setup is each website needs to have its own external IP, they cannot share. Thus each get's its own load balancer(ALB). I cannot deploy to my staging and then to production because of this.
Again, sorry for having to hit you up directly.
1180c1b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed, this commit is causing us problems as well. We need an ASG to be attached multiple times to a target group because of multiple applications running on our instances with different ports.