Error creating Azure resources when using New-WinGetSource

[dahovey]

Brief description of your issue

When running New-WinGetSource I receive the following error:

Write-Error: C:\Users\dahov\Downloads\WinGet.RestSource-Winget.PowerShell.Source\WinGet.RestSource-Winget.PowerShell.Source\Library\New-WinGetSource.ps1:157
Line |
 157 |          New-ARMObjects -ARMObjects $ARMObjects -RestSourcePath $RestS …
     |          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Failed to create Azure object.

Name                           Value
----                           -----
Parameters                     {contentVersion, Parameters, $Schema}
Error
ObjectName                     winget2test
ParameterPath                  C:\projects\Parameters\applicationinsights.json
TemplatePath                   C:\Users\dahov\Downloads\WinGet.RestSource-Winget.PowerShell.Source\WinGet.RestSource-Winget.PowerShell.Source\Library\ARMTemplate\applicationinsights.json
ObjectType                     AppInsight
Parameters                     {contentVersion, Parameters, $Schema}
Error
ObjectName                     winget2test
ParameterPath                  C:\projects\Parameters\keyvault.json
TemplatePath                   C:\Users\dahov\Downloads\WinGet.RestSource-Winget.PowerShell.Source\WinGet.RestSource-Winget.PowerShell.Source\Library\ARMTemplate\keyvault.json
ObjectType                     Keyvault
Parameters                     {contentVersion, Parameters, $Schema}
Error
ObjectName                     winget2test
ParameterPath                  C:\projects\Parameters\storageaccount.json
TemplatePath                   C:\Users\dahov\Downloads\WinGet.RestSource-Winget.PowerShell.Source\WinGet.RestSource-Winget.PowerShell.Source\Library\ARMTemplate\storageaccount.json
ObjectType                     StorageAccount
Parameters                     {contentVersion, Parameters, $Schema}
Error
ObjectName                     winget2test
ParameterPath                  C:\projects\Parameters\asp.json
TemplatePath                   C:\Users\dahov\Downloads\WinGet.RestSource-Winget.PowerShell.Source\WinGet.RestSource-Winget.PowerShell.Source\Library\ARMTemplate\asp.json
ObjectType                     asp
Parameters                     {contentVersion, Parameters, $Schema}
Error
ObjectName                     winget2test
ParameterPath                  C:\projects\Parameters\cosmosdb.json
TemplatePath                   C:\Users\dahov\Downloads\WinGet.RestSource-Winget.PowerShell.Source\WinGet.RestSource-Winget.PowerShell.Source\Library\ARMTemplate\cosmosdb.json
ObjectType                     CosmosDBAccount
Parameters                     {contentVersion, Parameters, $Schema}
Error
ObjectName                     WinGet
ParameterPath                  C:\projects\Parameters\cosmosdb-sql.json
TemplatePath                   C:\Users\dahov\Downloads\WinGet.RestSource-Winget.PowerShell.Source\WinGet.RestSource-Winget.PowerShell.Source\Library\ARMTemplate\cosmosdb-sql.json
ObjectType                     CosmosDBDatabase
Parameters                     {contentVersion, Parameters, $Schema}
Error
ObjectName                     Manifests
ParameterPath                  C:\projects\Parameters\cosmosdb-sql-container.json
TemplatePath                   C:\Users\dahov\Downloads\WinGet.RestSource-Winget.PowerShell.Source\WinGet.RestSource-Winget.PowerShell.Source\Library\ARMTemplate\cosmosdb-sql-container.json
ObjectType                     CosmosDBContainer
Parameters                     {contentVersion, Parameters, $Schema}
Error
ObjectName                     winget2test
ParameterPath                  C:\projects\Parameters\azurefunction.json
TemplatePath                   C:\Users\dahov\Downloads\WinGet.RestSource-Winget.PowerShell.Source\WinGet.RestSource-Winget.PowerShell.Source\Library\ARMTemplate\azurefunction.json
ObjectType                     Function

Steps to reproduce

Following instructions here. Running below command (some values changed for security):

New-WinGetSource -Name winget2test -ResourceGroup rg-vnet01-wus2 -SubscriptionName "Test" -Region westus2

Expected behavior

More meaningful error should be provided or resources should be created as expected.

Actual behavior

Non-descript error received.

Environment

Windows Package Manager v1.1.12986
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22000.318
Package: Microsoft.DesktopAppInstaller v1.16.12986.0

[dahovey]

I forgot to add that some Azure resources are created, as shown below. It is not clear where the hang-up is.

[dahovey]

Another note is, the status of the Azure Cosmos DB Created by powershell is Failed.

[RDMacLachlan]

Hi @dahovey,

Thank you for reaching out with regards to your experience. I'd be happy to help you with this. The typical failure that occurs at this stage of deployment is that the name used is not unique for the specified Azure Resource being created.

Based on the information you've shared, I assume that there was a problem with the CosmosDB Account creation. Can you please refresh the view on the CosmosDB Account Overview page, and verify if the CosmosDB Container and Database were created or if the error refreshing the collection list goes away.

Thank you,
Roy

[dahovey]

It look me a while but I did finally get the resources created.

I tried a different Azure Region and it worked. It wasn't a naming conflict. My first experience working with Cosmos Db wasn't great.