APIM Classic Tiers Only - Add Support for v2 Tiers (Basic v2 / Standard v2 / Premium v2)

Open
#314 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
azure, csharp, powershell
Domain
api, cloud, infrastructure

Research direction

Start with the New-WinGetSource cmdlet and its underlying ARM templates, then trace how the ImplementationPerformance parameter selects the APIM tier. Add support for Basic v2, Standard v2, and Premium v2, and verify that deployments can support the stated private endpoint and VNet integration scenarios.

Written by the indexing model from the issue text.

Description

Issue-Feature
Description of the new feature / enhancement

The New-WinGetSource cmdlet and its underlying ARM templates only deploy classic APIM tiers (Developer, Basic, Standard) via the ImplementationPerformance parameter. The newer v2 tiers (Basic v2, Standard v2, Premium v2) — which are generally available and recommended for new deployments — are not supported.

This means private endpoint and VNet integration scenarios are impossible when APIM is deployed as part of the WinGet REST source, because:

  • Classic Developer / Basic / Standard do not support outbound VNet integration
  • Classic Developer supports inbound private endpoints (for testing only), but Classic Basic and Standard do not
  • Only Standard v2+ supports both inbound private endpoints and outbound VNet integration
Proposed technical implementation details
  1. Deploy a WinGet REST source with private endpoints: 
    New-WinGetSource -Name "corpwinget" -ResourceGroup "rg-winget" `
    -ImplementationPerformance "Basic" `
    -Region "westeurope"
  2. Note the APIM instance is deployed as Basic (classic).
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.