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

Untitled

`aws.getAutoscalingGroups` returns a Promise, you don't need to wrap that in an output. Just use `.then()` on it.

oh, interesting thought.  thank you.

i started with the example in the docs which did that but perhaps things have simplified since then.
<https://www.pulumi.com/docs/reference/pkg/aws/getautoscalinggroups/>

ok, that produced desirable results:
```Updating (dev):
     Type                       Name          Status      
     pulumi:pulumi:Stack        gcso-k8-dev               
 +   ├─ aws:ec2:LaunchTemplate  bar1-b806b39  created     
 +   └─ aws:ec2:LaunchTemplate  bar2-cd01f02  created     ```


i think i assumed that the portion of the example i used would work in my situation where i was trying to resolve the promise differently.  and i assumed that `pulumi.output()` actually handled promises.

`pulumi.output` does handle promises, but you have to resolve it with an `apply` (like `.then()` for Outputs)

See <https://www.pulumi.com/docs/intro/concepts/programming-model/#outputs> for more details

Related question: is there a benefit of wrapping the Promise with an Output in this case? The only one I can think of is that it allows a simple `pulumi.all` refer to the results, alongside lots of other outputs...

You can use Promises directly in the `all`, so it’s not necessary in this case.

For example:
```const foo = new Promise(resolve =&gt; resolve("foo"))
export const fooValue = pulumi.all([foo]).apply(([v]) =&gt; v)```
results in
```Outputs:
    fooValue: "foo"```

Interesting. Clearly I did not well grasp `pulumi.output` &amp; `.apply()`. I may experiment with this more. Thank you.
Seems to accomplish my stated example, I would probably need to stack the behavior as so:
1. preview and bulid ASGs in a way that I need a promise.
2. resolve the promise to query AWS for the ASGs.  i know that shouldn't be necessary but this is for testing behavior for a much larger project.
3. resolve the promise from #2 to begin building resources as a consequence of the returned ASG list.