As long as one can create resources and pass outputs between them, my coding goes fine and smooth. But for the n-th time, I'm struggling when I have to mix in a get function. Context: I have a regular Javascript function creating, first calling a get function and based on the output, creating 2 resources and returning me a

Promise

which I used correctly in my code. So far so good. I'm now trying to convert that function to a

pulumi.ComponentResource

subclass, where I have the get function and the resource creation as well. But in that move, it seems I broke the setup for correct async processing. When I try to refer to the outputs of my

ComponentResource

, they still seem to be

undefined

. Each output in my component is an output from each of the 2 child resources. Does anyone have an example of a

ComponentResource

which mixes a get function, resource creation based on the fetched info and exposing outputs on the component class?

Is it one of the get functions that returns a Promise, rather than an Output?

does this capture the issue? https://github.com/pulumi/pulumi/issues/5758

The important bit imo is that Promises returned from get functions like getAmi have to be wrapped in

pulumi.output()

@billowy-army-68599 that issue is indeed my mental tormentation. 🙂

@limited-rainbow-51650 i believe your experience is going to get much better here pretty soon 😄

@billowy-army-68599 you mean by applying the suggestion from @little-cartoon-10569, or by you and your colleagues fixing that issue? 😄

by making the experience better, accepting outputs in functions

The functions now have $fnOutput forms that return an Output, and accept Input/Output in arguments; these forms behave similarly to what you would do by mechanically wrapping promise-returning functions with an apply block. This should be available in TypeScript already, we are just waiting on languages like C# to land support before making an official blog post about it.

@enough-garden-22763 which minimal version of Pulumi has this for NodeJS?

The relevant version here is version of providers.

In my case, I will have to search for versions of the GCP (classic) and Kubernetes providers to have this.

https://github.com/pulumi/pulumi-gcp/blob/master/sdk/nodejs/secretmanager/getSecretVersion.ts#L90 for gcp

@enough-garden-22763 with all the help I got so far, I was able to fix it. I will definitely start to use the new function Output functionality ASAP. It simplifies the coding a lot!