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

If you still have the stacks around for the old resources, then destroying those stacks is best.

If you don't or if somehow these resources became orphaned from the stack that created them, there’s no built-in way today to force replace the existing resource.  This feature request is very similar (or maybe the same) to <https://github.com/pulumi/pulumi-kubernetes/issues/264>, which is one of the most requested improvements for the Pulumi Kubernetes provider, which I expect we’ll relook at addressing soon.