So essentially a ComponentResource would be part of that “superstack” right?

I found this blog: https://www.pulumi.com/blog/creating-and-reusing-cloud-components-using-package-managers/#resource-components which seems a bit related

can a ComponentResource leverage a StackReference and/or aggregate all resources of child stacks without impacting the child stacks? e.g. 2 reqs: 1.) A user wants to be able to deploy a single instance/variation of this application so it would have its own unique stack, I gather. 2.) A user wants to be able to deploy all or more instances/variations of this application, but somehow, if possible, having the individual stack state preserved.

#2 might be more difficult unless there’s some secret stuff I’m missing. but I think it would be acceptable for the state to change if using the “aggregate” stack to deploy multiple resources. It just means any affected child stacks would be ‘stale’ at that point and vice-versa…

I'm not following 2: i'm afraid

The idea is that #2 is when the user wants to deploy “all variations” of the particular application to be able to deploy them atomically, say using the ComponentResource, but each variation would be deployed to its own unique stack so that change is tracked for the variation.

Maybe this can be distilled: can a ComponentResource deploy sub-stacks?.. is sub-stacks the right term to use here?

https://github.com/pulumi/pulumi/issues/2209 maybe this is what I’m seeking, and it’s not implemented?

I think what Luke is describing in this issue is what I’m seeking, but it looks like it’s not implemented. 🤔