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 need to double check, but this would only happen on resource creation I think, does the resource you’re using for `ApplyT` already exist?

Yes, it does. Looks like we were running our code on creation, not on subsequent no-op reconciliations, and the way ApplyT works obscured an error that was happening as well. Looks like using stack exports and handling this outside of our Pulumi program is gonna be a bit nicer, in this case