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

That shouldn't happen :confused: <@UB27BHS4B> just fixed a similar sounding issue last week, I wonder if it's the same problem. <@U84HBHXS8> may also know.

<@UB39JFCKC> Can you share details of the `panic` you see on Update? I think I can suggest a way to get unblocked, but would help to know exactly what panic you are hitting.

Actually I just found out that `pulumi refresh` error was valid: there were duplicate bucket objects created - same name but different postfix IDs.

Now `refresh` succeeds, and then `update` succeeds too

Not sure how I got duplicated objects, but they were created by pulumi at some point. Deleted duplicates manually.

Were they marked pending delete? That can happen if a replacement operation gets interrupted. That's the bug Sean just fixed (relaxed the assertion). I don't know if we cut a new CLI with the fix yet, but we should.

Umm... they looked normal :slightly_smiling_face: and I believe I interrupted Function creation

Yes - this means there were pending deletes - and <@UB39JFCKC> is hitting a few of this issues linked from <https://github.com/pulumi/pulumi/issues/1645>.

The workaround here is to do the following:
1. `pulumi stack export &gt; stack.json`
2. Edit `stack.json` to remove the entries in the `resources` list that are marked `"delete": true` and make note of the IDs of anything you delete like this.
3. Run `pulumi sack import &lt; stack.json`

This process will make Pulumi "forget" about these resources, and then you will want to clean them up in the GCP console.  

Of course, we should have never let you get in this state, and that's what the above issue and it's sub-issues are tracking.

Ah, now I remember I've seen some "delete" resources popping up in console earlier. Not in the last runs though... That's probably related anyway.

Sorry that you’ve run into this! Pending deletes are a big pain point in our system and I’m tracking a bunch of usability issues in the issue Luke linked

<@UB3BGTV63> While you are here :slightly_smiling_face: Is there no way to create python Function in GCP through pulumi? I don't see the support in terraform, so probably the answer is no.

It should always be OK to delete any resource with the “delete”: true property in a stack. You’ll have to delete those manually in the GCP console, but they have already been replaced by other resources.

<@UB39JFCKC> The 0.14.3 CLI that just got released has a fix for the particular issue you ran into

&gt; Is there no way to create python Function in GCP through pulumi? I don't see the support in terraform, so probably the answer is no.

Yes - I believe this is correct.  Python support in Google Cloud Functions is still in beta, which may be part of the reason it is not (yet) in the terraform provider.

Would be cool to have some sort of generic way to get/set "custom" properties not known to pulumi. Otherwise the latest tech will often be blocked by release cadence. Not sure if that's feasible in any way.