https://pulumi.com logo
#general
Title
# general
b

billions-lock-73409

03/13/2019, 6:39 PM
Stepped away from a project for a while, and now when running my update I get the following error regarding my applicaiton load balancer and listener:
Copy code
Diagnostics:
  aws:ec2:SecurityGroupRule (https-external-0-ingress):
    error: aws:ec2/securityGroupRule:SecurityGroupRule resource 'https-external-0-ingress' has a problem: "description" cannot be longer than 255 characters: "Externally available at port Calling [toString] on an [Output<T>] is not supported.\n\nTo get the value of an Output<T> as an Output<string> consider either:\n1: o.apply(v => `prefix${v}suffix`)\n2: pulumi.interpolate `prefix${v}suffix`\n\nSee <https://pulumi.io/help/outputs> for more details.\nThis function may throw in a future version of @pulumi/pulumi."
Here is the code for this specific piece:
Copy code
const appListener = loadBalancer
    .createTargetGroup(`probot-target-${env}`, {
        port: 3000,
        protocol: 'HTTP',
        healthCheck: { path: '/probot' },
        deregistrationDelay: 30,
    })
    .createListener('https', {
        certificateArn: secretsCert.arn,
        protocol: 'HTTPS',
        port: 443,
        sslPolicy: 'ELBSecurityPolicy-2016-08',
    });
Looks like the description is being auto generated somewhere, and trying to get the string value of an Output
c

creamy-potato-29402

03/13/2019, 6:51 PM
cc @lemon-spoon-91807
l

lemon-spoon-91807

03/13/2019, 6:51 PM
ack!
b

billions-lock-73409

03/13/2019, 6:51 PM
Also here are the versions I have installed of the packages
Copy code
"@pulumi/aws": "^0.16.10",
        "@pulumi/awsx": "^0.16.5",
        "@pulumi/cloud": "^0.16.2",
        "@pulumi/cloud-aws": "^0.16.2",
        "@pulumi/pulumi": "^0.16.19",
l

lemon-spoon-91807

03/13/2019, 6:51 PM
Lookin right now
👍 1
b

billions-lock-73409

03/13/2019, 6:52 PM
I noticed there were some changes with releases and 0.17, I can try bumping up to that but noticed it wasn’t released just yet
l

lemon-spoon-91807

03/13/2019, 6:55 PM
yup. this is totally my fault. fixing now
can provide you with a very hacky workaround in the meantime (involves editing package code)
let me talk to team about how we can release an 0.16 package as well
so i can fix in both places.
b

billions-lock-73409

03/13/2019, 6:56 PM
Okay, I’m fine waiting a bit if needed. let me know if I can help out or test
l

lemon-spoon-91807

03/13/2019, 6:58 PM
Also porting to 0.16.6
b

billions-lock-73409

03/13/2019, 7:07 PM
ok sweet
l

lemon-spoon-91807

03/13/2019, 7:12 PM
Ok. Should hopefully have out by EOD barring CI/CD issues.
If you need a workaround, see the PR and make that change in your
@pulumi/awsx
package manually.
b

billions-lock-73409

03/13/2019, 7:18 PM
Ok will do, thanks for the quick fix 👍
l

lemon-spoon-91807

03/13/2019, 7:19 PM
of course. really sorry for the frustration
b

billions-lock-73409

03/13/2019, 7:22 PM
all good, no frustration here 🙂
l

lemon-spoon-91807

03/13/2019, 10:19 PM
awsx: 0.16.6 is available now
b

billions-lock-73409

03/15/2019, 7:35 PM
ty!