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

You're correct - it is a bit confusing and not well-documented.

The primary function of `register_outputs()` is to register that your component is "done" to the Pulumi engine. This is necessary for Pulumi to handle dependencies of your component correctly.

You do still need member variables on the component itself to use its outputs in other places in your Pulumi application - e.g. <https://github.com/pulumi/examples/blob/f0732dc6314636f48a88b4ac4da55e3187b1def4/kubernetes-py-jenkins/jenkins.py#L213>.

Oh thank you.
So I’ve seen people using it as `register_outputs({})` without listing the actual outputs.

Apparently, it works for them. Then what difference does it make to specify output properties in this function call?

<@UDEJ1F5SQ> `...is to register that your component is "done"` What would be a best practice if my component has multiple resources? e.g.: A custom component that creates a security_group &amp; ec2 instance... should I register at least 1 output for both resources? :thinking_face: