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

When you say pulumi refresh doesn't work, can you elaborate?

as I understand it `pulumi refresh` inspects the stack and the script, and tries to bring them together. So if the app doesn't have a resource described, and the cluster doesn't have it, but the stack _does_ have that resource, it would remove it from the stack.

As an example, I have removed certmanager from the script, and it was removed from the cluster, but the stack seems to still think that all of the certmanager resources are still present.

image.png

Currently the script does not have a cert-manager chart defined anywhere, the cluster does not have any cert-manager resources, so this picture of the stack and resources is incorrect and I would expect `pulumi refresh` to fix that.

So we have exported the stack to a .json file and we've manually removed all of the dangling resources and re-imported it and that seems to have worked.

Yes, I would have expected `pulumi refresh` to fix that too.

To expand a bit on the behavior you described... if you have a resource in your Pulumi state, but that resource does not exist in your provider, `pulumi refresh` should "fix" that, meaning recognize the resource no longer exists and remove from your state file.

Having said that, I believe the `v3:Chart` resource itself is a component resource in Pulumi's terms, so it does not exist in that exact form in your k8s cluster.

So `pulumi refresh` should have removed any of the sub-resources of that chart (if they no longer existed), but the chart component might not be removed. I'll need to confirm the "component refresh" behavior with a Pulumi engineer.

Thanks <@UDEJ1F5SQ> for looking into it. I recently updated to the latest CLI so I was a bit concerned a regression had been introduced.

I've never had to manually manipulate the export of a stack to get to "clean".