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

Hello! In developing some custom python Components, I realized `register_outputs`  does very little for sharing outputs of the Component. As discussed here: <https://github.com/pulumi/pulumi/issues/2653>. That’s fine and makes sense (kind of lol). My question is, is there actually anything wrong/dangerous with calling `pulumi.export(…)` within a Component, instead of in the main program, other than the Component consumer may not actually want that export?

It breaks all hope of unit testing the component..

export is really for stack outputs, so you probably don't want to be calling that in components.

That’s what I figured. thanks. Would it be helpful or is there any interest in somehow making that preventable?

Linting tools help with that, if it's important to you. And code reviews.
I have a code standard that no external interfaces (config, stack references, other components, etc.) are allowed in components we write, other than the component's core purpose and logging. We rely only on code reviews to enforce this. It's working fine so far.