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

Wrapping both in an output should give you the same effect for both, to get the projectId you would do `project.apply(p =&gt; p.projectId)`

One will unwrap the promise to an output of the object with primitives and the other will traverse the object to have all the outputs as primitives during the apply

But in Typescript, what is the common “type” here I can set in my component constructor? I hope not `any`.

`constructor(project: &lt;which type here?&gt;)`

I'm not sure if what those types resolve actually intersect but going for the safe route you could do `Input&lt;Project|GetProjectResult&gt;` and then do `project = output(project)` before using it on your component

Your `|` character made me think about having `or`-types to indicate one or the other:
`constructor(project: gcp.organizations.Project | Promise&lt;gcp.organizations.GetProjectResult&gt;)`
My editor is not complaining… will see how far I can get with this.

I would still prefer using `Input` wrapping them on the argument list to allow the values to be passed both directly, as promise or as output

Why do you prefer it that way? Because it is clearer referring to an `Input` or is there also another technical thing I’m missing here?

```getSomeConfigsExternally().then(config =&gt; new Project(projectId: config.projectId))```