https://pulumi.com logo
#dotnet
Title
# dotnet
f

fast-vr-6049

07/27/2023, 10:19 PM
Hey folks! Has anyone had any success with using a
StringBuilder
with
Output<string>
objects? I'm trying to create a large string using a mix of `string`s and `Output<string>`s, and I'm scratching my head on how to make use of
StringBuilder
for this purpose
c

colossal-plastic-81954

07/28/2023, 6:54 AM
The Output<string> is like a Task<string>: 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<T>. https://www.pulumi.com/docs/concepts/inputs-outputs/#apply Inside the Apply, you can use the StringBuilder as usual.
e

echoing-dinner-19531

07/28/2023, 9:04 AM
Mixing these is probably tricky, Apply's run async and you really don't want to mix that with mutable state.
f

fast-vr-6049

07/31/2023, 7:03 PM
Thanks for the reply, both! @echoing-dinner-19531 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<string>`s, into a single large string (it'll become a
.conf
file). Assembling all of these secrets gives me one large
Output<string>
. So far, so good. However, the
Source
parameter of the
Blob
resource accepts an
Input<AssetOrArchive>
. I want to put this big
Output<string>
into a
StringAsset
object (which inherits
AssetOrArchive
via
Asset
), but the only type it accepts is
string
, not
Output<string>
. If I construct this
StringAsset
inside an
Output.Apply
and get an
Output<StringAsset>
, Blob's
Source
parameter rejects it. It states that it cannot convert an
Output<StringAsset>
into
Input<AssetOrArchive>
, 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<T>
into an Azure Blob.
Just in case, I've logged a Github issue about this: https://github.com/pulumi/pulumi-azure-native/issues/2621
e

echoing-dinner-19531

08/01/2023, 7:51 AM
Yeh... that sounds like an oversight of the asset code. It should be fine with Output<string>, 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.
f

fast-vr-6049

08/01/2023, 4:26 PM
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 😓
2 Views