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

The Output&lt;string&gt; is like a Task&lt;string&gt;: it's something that eventually will be resolved into a string. So you can't use it as a regular string. The way to use it, is to use the Apply method on an Output&lt;T&gt;.

<https://www.pulumi.com/docs/concepts/inputs-outputs/#apply>

Inside the Apply, you can use the StringBuilder as usual.

Mixing these is probably tricky, Apply's run async and you _really_ don't want to mix that with mutable state.

Thanks for the reply, both! <@U02J3T6A8LB> I hope you don't mind me direct mentioning you on this, but I ran into an issue that getting insight from a Pulumi engineer on it would be appreciated!

I'm trying to populate a config file that contains secrets, and upload it to Azure Blob Storage for use in an Azure App Gallery Application. To do this, I need to aggregate some disparate secrets, which are `Output&lt;string&gt;`s, into a single large string (it'll become a `.conf` file). Assembling all of these secrets gives me one large `Output&lt;string&gt;`. So far, so good. However, the `Source` parameter of the `Blob` resource accepts an `Input&lt;AssetOrArchive&gt;`. I want to put this big `Output&lt;string&gt;` into a `StringAsset` object (which inherits `AssetOrArchive` via `Asset`), but the only type it accepts is `string`, not `Output&lt;string&gt;`. If I construct this `StringAsset` inside an `Output.Apply` and get an `Output&lt;StringAsset&gt;`, Blob's `Source` parameter rejects it. It states that it cannot convert an `Output&lt;StringAsset&gt;` into `Input&lt;AssetOrArchive&gt;`, despite the types being completely compatible from what I can tell. Am I doing something wrong here, or have I run into a bug? If I'm not doing something wrong, this would suggest to me that there's currently no way to put an `Output&lt;T&gt;` into an Azure Blob.

Just in case, I've logged a Github issue about this: <https://github.com/pulumi/pulumi-azure-native/issues/2621>

Yeh... that sounds like an oversight of the asset code. It _should_ be fine with Output&lt;string&gt;, but I think we just haven't filled that in. I'll reply on the ticket as well.

Ah I see others have already replied that it was just a type inference issue, I'll ponder if we can do anything to make that easier, but at least it works.

Thanks! Yeah, the only way I can think of that could resolve that would be making use of interfaces instead of abstract classes, but that'd probably be a significant rewrite :sweat: