From c51ec92db223faa0ef76913ae6ee6ec445423fd1 Mon Sep 17 00:00:00 2001 From: Peter Williams Date: Sat, 21 Oct 2023 18:48:55 -0400 Subject: [PATCH] prod/constellations-cosmosdb.tf: sync up with db restoration So, after creating this CosmosDB instance, I deleted it and created one in the Azure Portal by restoring a backup of the development database. The "new" database appears to be a bit weird, but it also does seem to be populated with the content put together in the dev site. It might be necessary that a "database migration" would have been a better way to do this, but we'll see how well things work as is. --- prod/constellations-cosmosdb.tf | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/prod/constellations-cosmosdb.tf b/prod/constellations-cosmosdb.tf index d8e07f2..949f8a3 100644 --- a/prod/constellations-cosmosdb.tf +++ b/prod/constellations-cosmosdb.tf @@ -36,6 +36,11 @@ resource "azurerm_cosmosdb_account" "cx_backend" { max_interval_in_seconds = 5 max_staleness_prefix = 100 } + + restore { + restore_timestamp_in_utc = "2023-10-21T21:00:00Z" + source_cosmosdb_account_id = "/subscriptions/581389a3-e46e-43a4-bef4-4d0c1c43e6a6/providers/Microsoft.DocumentDB/locations/westus/restorableDatabaseAccounts/56fc946b-0a0b-4674-9f05-0f2b8cd73b69" + } } # Supporting vnet/private-endpoint stuff