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

yeah it's kind of forgotten function. If you want stack outputs I'd strongly recommend creating the stack outputs *only* in `__main__.py` otherwise you'll run into problems

we do have mostly our custom classes inheriting from `pulumi.ResourceComponent`, doing `pulumi.export` in those classes `__init__` seems to work pretty well

I just hope it won't bite you back because with `pulumi.export` you are literally exposing a local value globally.

And it is just waiting for a name clash in the `exports` dictionary.

it also makes searching for the orging where the export came from very difficult