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

You're not doing anything wrong :slightly_smiling_face: AWS has created a resource that Pulumi doesn't know about (e.g. a new version of the component) and when you edit the component, Pulumi tries to delete-then-create, but the delete is being blocked by AWS.

Your options are to find and delete the mystery resource (I find that using the console to attempt to delete the known resource usually produces a more useful error message); or change the way you manage component versions to not delete old versions, just add new ones.

(Aside: when adding large blocks of text or code, the Text Snippet tool in the lightning menu is great: it collapses nicely for a better reader/scroller experience.)

<@U012UJTT55M> thanks for your reply, I’m wonder why pulumi can not delete the old component,
You are completely right about the reason (existing dependency), but there is no any dependency that pulumi not aware of - component, imagepipeline, image recipe - all of them created via pulumi,
so we can no just to delete it?
I’m new to pulumi, and trying to understand if this is expected behaviour or not

If Pulumi knows about it, then it will delete it. Maybe it doesn't know that one resource has to be deleted before another? That does happen. There's a _dependsOn_ opt that can be used if that's the problem.