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

My actual example is Event Grid subscriptions in Azure (though it would apply to SNS subscriptions in AWS)

No. You cannot move resources between stacks like that. You can grab a resource's ID from another stack and create a read-only version of the resource, and make that the parent... but that's liable to cause problems later (e.g. when deleting resources).

But the parent attribute doesn't mean anything important at the provider level. It's only used for drawing resource graphs (e.g. in _pulumi preview_) and opt-inheritance. Just go with null parent, or _this_ if it's in a ComponentResource.

Ah gotcha. Can a read-only parent have a read-write child?

Also, if it's read only in the child stack I'm assuming the only way of getting it into state is by doing a refresh?

Yes, afaik the writiness of a resources is not inherited :slightly_smiling_face:

No, it's a full resource, but it doesn't provision/update it. Onesec I'll find the docs.

Heh, it's not documented as a separate concept. Just the _get_ functions in each resource. <https://www.pulumi.com/docs/reference/pkg/azure/eventgrid/eventsubscription/#look-up>

So you'd need the _id_ to be passed by StackReference, then use it in the 2nd stack. The _name_ doesn't have to match and could be used to emphasize that it is a read-only resource managed in a different stack.

Awesome that gives me enough to go off. Thanks for your help