New-WinGetSource fails if resource group region doesn't support classic App Insights

Open
#176 3 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

Assessment

This issue has not been assessed yet.

Description

Issue-Bug
Brief description of your issue

Classic mode for Application Insights will be deprecated in 2024, and there's several regions that don't support it. If the created resource group is in one of those regions, the New-WinGetSource cmdlet will fail with an error like this:

Line |
 157 |          New-ARMObjects -ARMObjects $ARMObjects -RestSourcePath $RestS …
     |          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Failed to create Azure object. 13:28:01 - The deployment 'applicationinsights' failed with error(s). Showing 1 out of 1 error(s). Status Message: Region doesn't support Classic resource mode for Application Insights
     | resources. Please use Workspace-based mode. (Code:BadRequest)  CorrelationId: daf01282-078d-4ee0-b24e-84782f2ccda5
Steps to reproduce

Run New-WinGetSource with a resource group in a region that doesn't support classic App Insights (such as westus3).

Expected behavior

Application Insights creation should use Workspace mode

Actual behavior

Failure

Environment
N/A
Dominant language
C#
Stars
317
Forks
79
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/winget-cli-restsource

All issues in microsoft/winget-cli-restsource

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.