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

i have an edge-case-ish question about cross account permissions and pulumi’s autogenerated resource name suffixes: how do people deal with rebuilds that cause resource renames?

considering the external account will have policies based on the full resource name which won’t be automatically updated by a rebuild of the resource being shared

Disclaimer: I don’t work for Pulumi.

I think the solution here is to turn autonaming off and add `deleteBeforeReplace.`

If the only thing that is changing is the name and not the resource, you could also use <https://www.pulumi.com/docs/intro/concepts/resources/#aliases|alias>.  Here is a blog called <https://www.pulumi.com/blog/cumundi-guest-post/|Refactoring Pulumi Code with `aliases`>