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

Aliases might help here: <https://www.pulumi.com/docs/concepts/options/aliases/>

Aliases are exactly the solution here.
If the code you want to add the alias to is outside of the current code base (which it can be if you define your reusable component resources in a dependent package or similar), you can do the aliasing via transformations, and keep it all in the current codebase.

okay, i will look at that! since you're being so extremely helpful. we often have the pulumi generated dependency tree "shift" and parent/depends-on will be different if we do not specifically set it. is it possible to have a dynamically generated file that we can see/validate with the dependencies? similar to a go.mod file?

e.g. if we're going to treat infrastructure like software, maybe dependency treeds should be handled the same?

Hmm, shifting parent/depends-on seems like unusual/unexpected. Are you able to share any code snippets we could use to try to replicate this behavior?