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

index.ts

<@UPA9DFVUH> 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

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")```

pulumi manages the Output in exports for you

I put it like that for sake of simplicity

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

so I can only use apply() for that purpose

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";```

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

<@UPA9DFVUH> 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";
})();```

&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

&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)

Thanks a lot <@UPA9DFVUH>
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.

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

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