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.

Pulumi Community

It seems to happen anywhere theres more than one item being interpolated.

I'm on tf framework version v1.1.1, and pf bridge version `<http://github.com/pulumi/pulumi-terraform-bridge/pkg/tfpfbridge|github.com/pulumi/pulumi-terraform-bridge/pkg/tfpfbridge> v0.0.0-20230120143314-6ffb2faf051e`

Yes this doesn't seem right, looks like a bug in the bridge. Mind helping me figure out how to repro? What's the type of "args.endpoint" in TypeScript?

so `args.endpoint` is a `pulumi.Input&lt;string&gt;` but its constructed from an interpolate that takes &gt;1 item:
```endpoint: pulumi.interpolate`vm-${vmPrefix}.${standaloneCluster.dnsDomain}```

those two are `pulumi.Output&lt;string&gt;` and `pulumi.Input&lt;string&gt;` respectively

if i do an apply(console.log) i get a normal looking string back.

Got it, I'll try to repro, possibly something with first-class output support on the wire.

<https://github.com/pulumi/pulumi-terraform-bridge/issues/812>

should i pull in a later version of the bridge and rebuild? just so we have parity

yeah for sure. ok i'll do that and see if anything changes

Hey Anton, confirmed issue still exists in pf/v0.2.1