This message was deleted.

sparse-intern-71089

09/19/2022, 10:15 PM

This message was deleted.

little-cartoon-10569

09/19/2022, 10:42 PM

Things can get created in the repo that aren't managed by Pulumi. Which means, Pulumi can't delete them. AWS has a requirement that the repo must be empty before it can be deleted.

little-cartoon-10569

09/19/2022, 10:43 PM

You either need to create all items in the repo through Pulumi (so that

pulumi destroy

knows to delete them), or else you need remove them from the repo before running

pulumi destroy

little-cartoon-10569

09/19/2022, 10:49 PM

Aside: you don't need

pulumi.output()

there. All that does is wrap the imageName (which is an Output<string>) in another Output<string>.

wide-wire-45375

09/19/2022, 11:08 PM

@little-cartoon-10569 thanks for your reply. The thing is, my image and the ecr repo both were created through pulumi. In other stacks with similar structure, the

pulumi destroy

works perfectly. But, in some cases it doesn't work.

wide-wire-45375

09/19/2022, 11:13 PM

currently, I have to delete the image (which was created through pulumi) from aws dashboard, then use the

pulumi destroy

command.

wide-wire-45375

09/19/2022, 11:16 PM

But for other stacks

pulumi destroy

removes the repo with the images with out any issue.

little-cartoon-10569

09/19/2022, 11:48 PM

This would happen if anything that isn't Pulumi is putting resources into the repo. For example, is anyone doing a

docker push

wide-wire-45375

09/20/2022, 5:09 AM

@little-cartoon-10569 no. I'm the sole user within the namespace. No one else can push into the repo.

352 Views

Open in Slack

Previous Next

Pulumi Community

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.