microsoft / microsoft/vscode-azurecontainerapps
Deploy from workspace creates a registry each time it fails
Open
Nobody has claimed this yet.
enhancement
needs discussion
- Dominant language
- TypeScript
- Stars
- 42
- Forks
- 21
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 2
Description
Repro steps:
- Open a project with a Dockerfile.
- Change the Dockerfile so that it won't build.
- Run Deploy project from workspace command.
- Azure resources are created, including an ACR.
- ACR build fails, the settings don't get saved.
- Run Deploy project from workspace again.
- Another ACR is created.
We should try to prevent this, perhaps saving the settings before a build is attempted, or detecting an existing ACR and using it (not sure if that's a good thing).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Deploy project from workspace command and trace the Azure resource and ACR build flow using the listed reproduction steps with an invalid Dockerfile. The fix is complete when a failed build does not cause a new ACR on retry, while the deployment settings remain available or an existing registry is reused.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript, vscode
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100