I got into situation when I need to use outputs from StackRe

Question

I got into situation when I need to use outputs from StackReference in components that also generate outputs and need to assign them to index ts module exports so they appear in stack output Once I wrap them in apply callback exports they were producing can t be assigned anymore Is there a clean way to work around this without writing promises that would register them in module exports once resolved

boundless-airport-99052 · Answer

This should works

boundless-airport-99052 · Answer

Could you give an example

acceptable-stone-35112 · Answer

Here s basic reproduction

acceptable-stone-35112 · Answer

< boundless airport 99052> its simple flow all stacks are in same project while dev qa prod whatever stacks need outputs of infra stack In console log you can see that module exports actually contains new property but in outer log and stack outputs its missing

boundless-airport-99052 · Answer

to export a value you don t have to use `apply` by the way in typescript I can t do `export` in a condition I should be to the top level But here is how I do ```import StackReference from pulumi pulumi const stackRef = new StackReference `$ <http config org|config org> $ pulumi getProject infra` exports infraStackName = stackRef requireOutput stack ```

boundless-airport-99052 · Answer

pulumi manages the Output in exports for you

acceptable-stone-35112 · Answer

I see

acceptable-stone-35112 · Answer

I put it like that for sake of simplicity

acceptable-stone-35112 · Answer

in actual project I pass outputs from stack ref to components that in turn generate outputs of their own and I need to propagate all of them to stack output

acceptable-stone-35112 · Answer

so I can only use apply for that purpose

acceptable-stone-35112 · Answer

And btw exports do work inside conditions e g following works fine in both if and switch case scope ```if pulumi getStack = infra exports test = 123 ```

acceptable-stone-35112 · Answer

the only case I see when exports don t have effect at module scope is inside apply callback

acceptable-stone-35112 · Answer

< boundless airport 99052> I guess it has something to do with applyHelperAsync didn t deep dive into that code yet e g following doesn t set exports ```setImmediate = gt exports test = ABC ``` while this one does ``` async = gt exports test = ABC ```

boundless-airport-99052 · Answer

gt And btw exports do work inside conditions gt e g following works fine in both if and switch case scope AFAIK it didn t with typescript

boundless-airport-99052 · Answer

gt in actual project I pass outputs from stack ref to components that in turn generate outputs of their own and I need to propagate all of them to stack output I don t understand what you do exactly but you don t need to use `apply` when you use `pulumi Input` and `pulumi Output`everywhere including your components

acceptable-stone-35112 · Answer

Thanks a lot < boundless airport 99052> I got your point and indeed passing Input lt string gt there instead of string solves the problem I used apply initially because the code was using discovery to get resource which returned strings for arns ids and components expected strings

acceptable-stone-35112 · Answer

I d prefer pulumi to provide global registry for stack outputs instead of relying on module exports so I can just register my outputs from any component

acceptable-stone-35112 · Answer

it would also be a language agnostic api common for all runtimes