Exposing "free tier" for CosmosDB to New-WinGetSource

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
azure, csharp
Domain
cloud, database

Research direction

Start by locating the New-WinGetSource entry point and the handling for the Demo, Basic, and Enhanced configurations. Determine how the CosmosDB free tier is currently selected for Demo; done means Basic and Enhanced can select it while respecting Azure's one-free-tier-instance-per-subscription restriction.

Written by the indexing model from the issue text.

Description

Issue-Feature
Description of the new feature / enhancement

Three configurations are supported in the New-WinGetSource.

Currently, only the Demo configuration uses the free tier of CosmosDB.

Note: Azure restricts a single instance of the CosmostDB free tier per Azure Subscription.

This would extend selecting the CosmostDB free tier to Basic, and Enhanced configurations.

Proposed technical implementation details

No response

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.