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

Hi everyone, how can prevent I partial creation of a resource?
In my case it happens for a database account.  `pulumi up` failed for some reason in the first run, and the database account managed to slip through. Subsequent `pulumi up` tried to create that same resource and failed because of name uniqueness.
`pulumi refresh` didn't work either
How can I handle this?

What was the failure?  If the resource creation fails without reporting back the id of the resource, there is no way for Pulumi to track the existence of the leaked resource. We go to lengths to ensure we never lose track of a created resource in the Pulumi layer - but there may be bugs in underlying clouds or upstream resource providers that could lead to this. If you have a repro - opening an issue would be great. 

Thanks <@UB3BGTV63>, I couldn't repro the issue since then.