This message was deleted.
# generals
sparse-intern-71089
03/21/2019, 1:54 AMThis message was deleted.
l
lemon-spoon-91807
03/21/2019, 1:54 AMick, that's written badly. it should have that as the default, but allow you to specify TLS.
lemon-spoon-91807
03/21/2019, 1:54 AMi'll fix tonight
lemon-spoon-91807
03/21/2019, 1:55 AMwe're planning on pushing a new release hopefully tomorrow
lemon-spoon-91807
03/21/2019, 1:55 AMsorry about that!
a
adamant-dress-73325
03/21/2019, 1:58 AMNo worries! Pulumi dev experience has been pretty amazing, awsx is quite an improvement over Cloud.Service for me.
l
lemon-spoon-91807
03/21/2019, 2:00 AMgreat to hear!
lemon-spoon-91807
03/22/2019, 5:04 PMHey Richard! are you there? the 0.17.1 release of awsx now supports this
lemon-spoon-91807
03/22/2019, 5:05 PMif you're on 0.17 already, then this should be trivial to move to
lemon-spoon-91807
03/22/2019, 5:05 PMif you're on 0.16 though, moving to 0.17 is a larger sort of change, so i would be more conscientious about moving forward.
a
adamant-dress-73325
03/22/2019, 6:22 PMThanks, I’m on 0.17 will try it out later
adamant-dress-73325
03/23/2019, 7:28 PMAlright, almost working, but need certificateARN added to the args. Following does not type-check:
Copy code
const worthTLSListener = worthTargetGroup.createListener("sandbox_worth", {
port: 443,
protocol: "TLS",
certificateArn: worthCert.arn,
sslPolicy: "ELBSecurityPolicy-2016-08"
});adamant-dress-73325
03/23/2019, 7:30 PMAlso protocols should be limited to
TCP, TLSl
lemon-spoon-91807
03/25/2019, 5:55 PM@adamant-dress-73325 These have gone through. I'm creating a new tagged release for you to use
a
adamant-dress-73325
03/25/2019, 5:56 PMThanks 👍
l
lemon-spoon-91807
03/25/2019, 5:57 PMand i think you're right about the protocols
lemon-spoon-91807
03/25/2019, 5:57 PMi can make that change later. but there's a high turnaroundtime getting releases out. so i can patch that afterwards
lemon-spoon-91807
03/25/2019, 6:00 PMAre you Blitz2145 btw?
lemon-spoon-91807
03/25/2019, 6:02 PMoh. same avatar image. so presumably yes 🙂
a
adamant-dress-73325
03/25/2019, 11:01 PMyup, thats me. Thanks for the release, will try to make some more PRs if I can get to them
adamant-dress-73325
03/25/2019, 11:39 PMGot another puzzle for you, create an ALB with HTTPS, then change that resource to an NLB with TLS, I cannot seem to get it to work, error message is:
Copy code
Resources:
+ 1 to create
- 8 to delete
+-1 to replace
3 changes. 40 unchanged
Do you want to perform this update? yes
Updating (sandbox-peopleticker-dev):
Type Name Status Info
pulumi:pulumi:Stack peopleticker-sandbox-peopleticker-dev
> ├─ aws:ec2:Vpc default-vpc read
├─ awsx:x:ec2:Vpc default-vpc
> │ ├─ aws:ec2:Subnet default-vpc-public-0 read
> │ └─ aws:ec2:Subnet default-vpc-public-1 read
└─ awsx:x:elasticloadbalancingv2:NetworkLoadBalancer sandbox_worth_load_balancer
└─ awsx:x:elasticloadbalancingv2:NetworkTargetGroup sandbox_worth_target_group
└─ awsx:x:elasticloadbalancingv2:NetworkListener sandbox_worth_redirect
+ └─ aws:elasticloadbalancingv2:Listener sandbox_worth_redirect **creating failed** 1 error
Diagnostics:
aws:elasticloadbalancingv2:Listener (sandbox_worth_redirect):
error: Plan apply failed: Error creating LB Listener: ValidationError: A certificate must be specified for TLS listeners
status code: 400, request id: d6c4bc53-4f56-11e9-aeb1-f3f67ccce013adamant-dress-73325
03/27/2019, 7:07 PM@lemon-spoon-91807 just checking to see if you saw this last issue I ran into, I can file a proper GitHub issue if ya need.
l
lemon-spoon-91807
03/27/2019, 7:09 PMfascinating
lemon-spoon-91807
03/27/2019, 7:09 PMi mean... they're totally different types, so i'ts not clear how they would have a relation
lemon-spoon-91807
03/27/2019, 7:09 PMi would expect it would be just a delete followed by a create.
lemon-spoon-91807
03/27/2019, 7:09 PMSuper dumb question, but you did provide the certificate right? 😄
a
adamant-dress-73325
03/27/2019, 7:22 PMI did lol
adamant-dress-73325
03/27/2019, 7:24 PMI’ll try to post a reproducible case when I get some time later today
l
lemon-spoon-91807
03/27/2019, 7:24 PMok...
lemon-spoon-91807
03/27/2019, 7:24 PMi honestly don't understand what could be the issue then
lemon-spoon-91807
03/27/2019, 7:24 PMignorin the change of ALB to NLB, are you just able to make an NLB that uses SSL+certificate?
a
adamant-dress-73325
03/27/2019, 7:30 PMYup, NLB creation worked with SSL+cert. It was only the transition from ALB -> NLB that did not work
l
lemon-spoon-91807
03/27/2019, 7:30 PMi....
lemon-spoon-91807
03/27/2019, 7:30 PMi have no idea...
lemon-spoon-91807
03/27/2019, 7:30 PMdo you have the logs for this
lemon-spoon-91807
03/27/2019, 7:30 PMthat is insane 🙂
a
adamant-dress-73325
03/27/2019, 7:31 PMI can collect more logs, I only recorded the pulumi output above. Just tell me how to make pulumi verbose
l
lemon-spoon-91807
03/27/2019, 7:31 PM--debug --verbose 7 --logtostderr
lemon-spoon-91807
03/27/2019, 7:35 PMcan you show me your code too?
lemon-spoon-91807
03/27/2019, 7:35 PMhow you passed the certificate arn
lemon-spoon-91807
03/27/2019, 7:36 PMlooking at terraform, they have a 5 min timeout on this
lemon-spoon-91807
03/27/2019, 7:36 PMso i'm wondering if it was an ephemeral issue wher ethe cert didn't properly get created and registered with teh LB in the appropraite amount of time
a
adamant-dress-73325
03/27/2019, 10:46 PMThis is the code I was running
adamant-dress-73325
03/27/2019, 10:47 PM Copy code
{
"name": "typescript",
"devDependencies": {
"@types/node": "10.14.3"
},
"dependencies": {
"@pulumi/aws": "0.17.1",
"@pulumi/awsx": "0.17.3",
"@pulumi/pulumi": "0.17.2"
}
}adamant-dress-73325
03/27/2019, 10:48 PM@lemon-spoon-91807 Here’s the code I was running, when I ran into the cert issue
3 Views