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

Output&lt;T&gt; is essentially like Promise&lt;T&gt;. Except that instead of `.then()` you have to use `.apply()` to access the unwrapped value.

yeah i know, but the output of an `apply` is another `Output&lt;T&gt;` whereas with a promise I can `await` it and access the underlying value at preview time

You can still access the value of Output at preview time if the value is known

Is there something that isn’t doing what you expect?

I don't think you can guarantee that stack outputs will be known at preview time. It wouldn't be safe to assume that the outputting stack is not currently being deployed...

Or even that the stack is local / on your machine. You could (and frequently, _are_) getting those outputs from a stack at <http://api.pulumi.com|api.pulumi.com> or S3. These have the same async requirements as deploying to a remote API or S3...

yeah that makes sense but wouldn't that same issue occur at deploy time too? ie if I'm deploying a resource in `Stack A`  using a stack output from `Stack B`, what happens if `Stack B` is deploying while `Stack A` is using that output?

how does `requireOutput()` behave in that scenario?

I, for one, am happy to trust our new Pulumi overlords! (that it'll be alright once Pulumi looks after resolving dependencies)