microsoft / microsoft/vscode-containers

Move "build in ACR" command to ACA extension

Open
#112 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Azure/ACR registries
Dominant language
TypeScript
Stars
139
Forks
87
Avg merge
9h 15m
Merged PRs (30d)
9

Description

The Azure Container Apps extension is soon adding a command to build images in ACR. Using this would allow us to remove several Azure packages as dependencies, improving load time and reducing bundle size.

TODO: do we want to remove the command entirely, or leave in a soft entry point like we currently have with "Deploy to ACA"?

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.

Research direction

Start by locating the existing "build in ACR" command and the Azure package dependencies it uses. Compare its current entry point with the existing "Deploy to ACA" soft entry point, then determine whether completion means removing the command or preserving a delegated entry point while reducing dependencies.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, typescript
Domain
cloud, devtools
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.