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

You can't. The most you can do is call `.Apply` and within the apply callback use the string, but keep in mind that callback may not always run at preview time (we might not know what the value of the output is at preview time)

<@U02J3T6A8LB> Thanks.
Can you share code example for how to get the string from within the Apply callback? I am unsure of how to do this :slightly_smiling_face:

There's an example in the docs <https://www.pulumi.com/docs/intro/concepts/inputs-outputs/#apply>
Apply takes a function delegate and passes the value of the Output&lt;string&gt; as the parameter to that delegate.
But keep in mind that Applys run asynchronously and may not even run during preview.

<@U02J3T6A8LB> I keep running into this issue

image.png

<@U02J3T6A8LB> I keep running into this problem

The result of Output.Apply is another Output. It's like how Task.ContinueWith returns another Task.

<@U02J3T6A8LB> So there is no option to just get the string from that task?

No because in general that string might not exist

How could we return a string for a resource output at preview time?

<@U02J3T6A8LB> But cant I just check if the string exists?

Guess I need to hard code the string then :slightly_smiling_face:

Yeh generally you want to avoid using outputs to make fixed strings, again there's some things we're thinking about to make this stuff easier but its a bit long off still

<@U02J3T6A8LB> Thanks for the explanation :slightly_smiling_face:

<@U02J3T6A8LB> Are outputs only supposed to be shown in the CLI output, not used in code?

Oh no you can use them in code, all resource inputs can be Outputs because our code can handle that at preview time an input might be unknown.

So it's quite common to like take an ID from one resource and use that to build another resource.

<@U02J3T6A8LB> That makes sense I have done that before