I filed a support ticket with DigitalOcean, will update here to share what I learn.

All of DigitalOcean’s regions are xxx# in name. Somewhere along the line Pulumi autonamed a region object, and now that’s stuck.

Sorry for not responding sooner — I’ve been swamped with work and have had little time for personal projects this week.

Oooh, the plot thickens. I remembered that the Pulumi stuff is basically dependent on the Terraform provider, so I set up a test Terraform environment and tried to import the bucket. Here’s what actually got imported:

~/digitalocean-terraform-test ❯❯❯ terraform state show digitalocean_spaces_bucket.foobar
# digitalocean_spaces_bucket.foobar:
resource "digitalocean_spaces_bucket" "foobar" {
    bucket_domain_name = "<http://pl-bucket-prod.sfo2.digitaloceanspaces.com|pl-bucket-prod.sfo2.digitaloceanspaces.com>"
    endpoint           = "<http://sfo2-zg02.digitaloceanspaces.com|sfo2-zg02.digitaloceanspaces.com>"
    id                 = "pl-bucket-prod"
    name               = "pl-bucket-prod"
    region             = "sfo2-zg02"
    urn                = "do:space:pl-bucket-prod"

    versioning {
        enabled = false
    }
}

Check out that region and endpoint! Fascinating! I updated my ticket with DigitalOcean asking them if it’s corrupted or what.