This message was deleted.

sparse-intern-71089

11/28/2021, 10:32 PM

This message was deleted.

little-cartoon-10569

11/28/2021, 11:09 PM

Generally: don't export objects from the Pulumi program.

green-school-95910

11/29/2021, 10:44 AM

The

private

flag is just a TS thing. It doesn't affect anything at runtime. Try the new

prefix that is a real private field for JS https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Private_class_fields

green-school-95910

11/29/2021, 10:49 AM

But I would still not generally export entire instances, make an object just with the properties you want to export:

Copy code

export const componentFoo = {
  propA: foo.propA,
  propB: foo.propB,
};

I prefer this way, but you can try the

field (I never tried, but I think it should work)

magnificent-lifeguard-15082

11/29/2021, 11:14 AM

Yeah that makes sense. Though honestly the Component was actually the unit of composition and encapsulation I was hoping I could use as "what should be shared".

magnificent-lifeguard-15082

11/29/2021, 11:15 AM

Feel like it might fit in with the scope of a component to more explicitly define it's output interface. Will try find time and draft a feature proposal

little-cartoon-10569

11/29/2021, 7:50 PM

I don't think it would be feasible. Too much happens in ComponentResource constructors. It's unlikely that a stack reference could construct a ComponentResource without side effects.

little-cartoon-10569

11/29/2021, 7:51 PM

And you certainly wouldn't want the resource to be constructed in two projects / stacks.

Open in Slack

Previous Next

Pulumi Community

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.