Hi! I'm creating a CosmosDB with multiple regions, that's the code:

const gcosmos = new azure.cosmosdb.Account(config.globalCosmosDb.name,
    {
        name: config.globalCosmosDb.name,
        resourceGroupName: resourceGroup.name,
        location: "northeurope",
        offerType: "Standard",
        geoLocations: [...config.globalCosmosDb.regions],
        consistencyPolicy: { consistencyLevel: "Session" }
    }
);

And the config in my stack yaml file:

regions:
  - location: "North Europe"
    failoverPriority: 0
  - location: "West US"
    failoverPriority: 1
  - location: "Southeast Asia"
    failoverPriority: 2

The problem is that if I change my config to add a new region, like:

regions:
  - location: "North Europe"
    failoverPriority: 0
  - location: "West US"
    failoverPriority: 1
  - location: "Southeast Asia"
    failoverPriority: 2
  - location: "Canada East"
    failoverPriority: 3

My

pulumi up

deletes my cosmosDb and creates again instead of just updating the geolocations property, like in the image. Am I doing something wrong? 🤔

seems like a bug to me

That’s how the terraform provider is currently implemented… I had a try to fix it a while ago, but cosmos exposed numerous problems while changing the number of regions, so I couldn’t complete the work with a reliable set of tests.

Oh, that's unfortunate. But thanks for the feedback guys!