agreeable-caravan-84210
04/13/2021, 12:17 PMdestroy
+ update
. On the other hand, Azure supports resources migration (through portal) but I'm guessing I'll need to edit the resources IDs in the stack files with the new subscription ID, is it worth the try? Thanksgentle-diamond-70147
04/13/2021, 2:19 PMdestroy
+ update
would likely be easiest if those resources can be thrown away.agreeable-caravan-84210
04/13/2021, 3:22 PMupdating urn:pulumi:myStack::myProject::azure:storage/account:Account::mystack: Error updating Azure Storage Account network_rules "mystack4cbe748": storage.AccountsClient#Update: Failure responding to request: StatusCode=404 -- Original Error: autorest/azure: Service returned an error. Status=404 Code="PatchResourceNotFound" Message="The resource '<https://management.azure.com/subscriptions/a5*******************************/resourceGroups/mystackmain229fd717/providers/Microsoft.Storage/storageAccounts/mystack4cbe748?api-version=2019-06-01>' was not found when performing the PATCH operation." Target="mystack4cbe748"
Either way, I won't be pursuing this method anymore since I've already started the destroy + update. I leave this here as insights for future issues.