I updated from these packages:

"@pulumi/pulumi": "0.16.17",
        "@pulumi/aws": "0.16.10",
        "@pulumi/awsx": "0.16.5"

to

{
  "@pulumi/pulumi": "0.17.2",
  "@pulumi/aws": "0.17.1",
  "@pulumi/awsx": "0.17.0"
}

and ran

pulumi up

. Received this exception:

error: aws:ec2/securityGroupRule:SecurityGroupRule resource 'nginx-lb-listener-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."
    error: aws:ec2/securityGroupRule:SecurityGroupRule resource 'nginx-lb-listener-external-0-ingress' has a problem: "description" doesn't comply with restrictions ("^[A-Za-z0-9 \\.\\_\\-\\:\\/\\(\\)\\#\\,\\@\\[\\]\\+\\=\\;\\{\\}\\!\\$\\*]*$"): "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."

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

or

pulumi.interpolate

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

description

?

I'm not setting a

description

anywhere. This may come from awsx?

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

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

We'll get a release out to address this.

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