This message was deleted.

sparse-intern-71089

03/20/2019, 10:40 PM

This message was deleted.

white-balloon-205

03/20/2019, 10:47 PM

This likely means you were using an

Output

inside the description of the

SecurityGroupRule

which would previously have been injecting

[object Object]

- but now injects a warning to try to catch problems like this earlier. I expect you just need an

apply

pulumi.interpolate

in here. Can you share the snippet of your code that sets the

description

full-dress-10026

03/20/2019, 10:48 PM

I'm not setting a

description

anywhere. This may come from awsx?

full-dress-10026

03/20/2019, 10:49 PM

I create the sg via

awsx.ec2.SecurityGroup

white-balloon-205

03/20/2019, 10:49 PM

Ahh - I see - this is ultimately this code: https://github.com/pulumi/pulumi-awsx/blob/9836dffd54e8b45c18b2ecd208dd4dc7935e2c90/nodejs/awsx/elasticloadbalancingv2/application.ts#L183

white-balloon-205

03/20/2019, 10:50 PM

Looks like this was recently fixed with https://github.com/pulumi/pulumi-awsx/commit/9836dffd54e8b45c18b2ecd208dd4dc7935e2c90#diff-691910385112928d2e153d0aca0e3184

white-balloon-205

03/20/2019, 10:50 PM

But that we haven't yet done a release with that fix. https://github.com/pulumi/pulumi-awsx/blob/master/CHANGELOG.md#0171-unreleased

full-dress-10026

03/20/2019, 10:50 PM

Gotcha. I'll wait for that then. Thanks.

white-balloon-205

03/20/2019, 10:50 PM

We'll get a release out to address this.

white-balloon-205

03/20/2019, 10:51 PM

cc @lemon-spoon-91807

lemon-spoon-91807

03/20/2019, 11:37 PM

Yup yup. Sorry i didn't see this until now. Luke has summed up the issue nicely.

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.