This message was deleted.

Hey Mitch. is this using the gcp-native provider?

I had to leave so I executed the command and left it running

did you get a "completed" event at the end?

no, that's why it was stuck in pending

so pulumi continuously polls the GCP API in order to determine that the resource got created. If it got interrupted, the resource might have created, but Pulumi can't determine its current state - that's how you end up with

pending_operations

- it's a safety mechanism to ensure you don't create duplicate/overriding resources. I'd recommend running through it again but waiting till the calls have completed. You should see your outputs resolved and the bucket created like this:

Do you want to perform this update? yes
Updating (dev):

     Type                   Name            Status
     pulumi:pulumi:Stack    quickstart-dev  created
 +   └─ gcp:storage:Bucket  my-bucket       created

Outputs:
  + bucketName: "<gs://my-bucket-62f8bc7>"

Resources:
    + 2 created

Duration: 3s

I'm running pulumi from my laptop so perhaps this would not have happened if I was running from a pipeline. I will continue to kick the tires. to fix this I had to do the export/import/delete stack/create stack.

it generally doesn't happen when running from a laptop either, it may be your laptop went to sleep, or was interrupted another way