Additional customization for ARM parameter files

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
azure, csharp
Domain
cli, cloud

Research direction

Start by reviewing the ARM templates in the release artifacts and the New-WinGetSource cmdlet. Determine how users should create or export parameter files for CosmosDB Max IO, Azure SKU selection, and resource names, then verify that New-WinGetSource accepts and applies those files during deployment.

Written by the indexing model from the issue text.

Description

Issue-Feature
Description of the new feature / enhancement

Azure Resource Manager (ARM) templates are currently provided in the release artifacts.

This work item is to enable a user to create or export ARM parameter files to customize the deployment configuration.

Examples include:
Max IO - for CosmosDB
Azure SKU selection - for Azure resources
Resource name customization

The New-WinGetSource cmdlet should also be extended to support using these ARM parameter files.

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.