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 think dynamic providers are serialized and saved as part of resources they deploy, so `delete` might execute the code that you had when first deployed it? Try with a clean one?

Can I ask Pulumi to refresh what it has serialized?

Whenever you run an update, the updated implementation of the dynamic provider will be serialized. 

`Pulumi destroy` does not run the program though, so it will just use whatever implementation of delete was last deployed. 

But I am doing pulumi up and it still seems to use the previous code

<@UB3BGTV63> What is even more confusing, I removed a comment that made that resource planned as delete and it pulumi up gave no errors. Then I copied that resource (the same type, the same params just different names), changed its name etc. And pulumi up created it. So I had 2 resources of the same type (NodeJSApp in my example). Then I comment new resource, it execute delete without any problem. I have one resource of that type. Now I comment that original resource and I still see the same error...