-
Notifications
You must be signed in to change notification settings - Fork 4k
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.
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
interface required when enabling SSL in NLB listener does not exist #5330
Labels
@aws-cdk/aws-elasticloadbalancing
Related to Amazon Elastic Load Balancing
bug
This issue is a bug.
needs-triage
This issue or PR still needs to be triaged.
p1
Comments
tommycha
added
bug
This issue is a bug.
needs-triage
This issue or PR still needs to be triaged.
labels
Dec 6, 2019
SomayaB
added
the
@aws-cdk/aws-elasticloadbalancing
Related to Amazon Elastic Load Balancing
label
Dec 9, 2019
I have the same problem. Is there any workaround until the bug gets fixed? |
Something like the following should tide you over: @jsii.implements(elbv2.INetworkListenerCertificateProps)
class Certificate:
def __init__(self, arn):
self.arn = arn
@property
def certificate_arn(self):
return self.arn |
rix0rrr
added a commit
that referenced
this issue
Dec 13, 2019
Finally model certificates in a consistent way, using an `IListenerCertificate` interface (it has to be an interface to be able to maintain backwards compatibility with the erroneously introduced `INetworkListenerCertificateProps` interface) and an implemention of it called `ListenerCertificate`. `ListenerCertificate` can currently be created from an ACM certificate, and in the future should also be creatable from an IAM certificate. Make it the same for ALB and NLBs. Fixes #5330.
mergify bot
pushed a commit
that referenced
this issue
Dec 13, 2019
Finally model certificates in a consistent way, using an `IListenerCertificate` interface (it has to be an interface to be able to maintain backwards compatibility with the erroneously introduced `INetworkListenerCertificateProps` interface) and an implemention of it called `ListenerCertificate`. `ListenerCertificate` can currently be created from an ACM certificate, and in the future should also be creatable from an IAM certificate. Make it the same for ALB and NLBs. Fixes #5330.
ed-at-work
pushed a commit
to ed-at-work/aws-cdk
that referenced
this issue
Dec 17, 2019
Finally model certificates in a consistent way, using an `IListenerCertificate` interface (it has to be an interface to be able to maintain backwards compatibility with the erroneously introduced `INetworkListenerCertificateProps` interface) and an implemention of it called `ListenerCertificate`. `ListenerCertificate` can currently be created from an ACM certificate, and in the future should also be creatable from an IAM certificate. Make it the same for ALB and NLBs. Fixes aws#5330.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
@aws-cdk/aws-elasticloadbalancing
Related to Amazon Elastic Load Balancing
bug
This issue is a bug.
needs-triage
This issue or PR still needs to be triaged.
p1
When enabling SSL in NLB listener interface
INetworkListenerCertificateProps
is required:However there is nothing that creates that interface.
Reproduction Steps
Error Log
Error: Resolution error: Resolution error: Trying to resolve() a Construct at ../Properties/certificates/0/node
Environment
Other
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: