microsoft / microsoft/vscode-azureresourcegroups

[CoR] Location field remains blank after deployment plan is generated with a selected region

Open
#1,636 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

AT-CTI CoR
Dominant language
TypeScript
Stars
78
Forks
55
Avg merge
16h 49m
Merged PRs (30d)
139

Description

OS: Win11 x64
VS Code Insider: 1.132.0-insider
Build Version: 0.12.8-alpha.0

Repro Steps:

  1. Create an Azure Project.
  2. Proceed to the Deployment stage.
  3. Select a deployment location (e.g. East US 2).
  4. Generate the deployment plan.
  5. Observe the Azure Deployment Plan page.

Expect:
The Location dropdown should display the selected deployment region.

Actual:
The deployment plan references the selected region (East US 2), but the Location field remains blank and continues to display "Select a location...".
Image

More Info:

  1. This issue is intermittent and does not reproduce consistently.
  2. The deployment plan already referenced East US 2 and the location had been selected earlier through the chat workflow. However, the Location field in the Deployment Plan UI appeared empty. After reselecting the same location value (East US 2) and approving the plan, the system treated it as a location update, regenerated deployment-plan.md, and requested another approval.

Contributor guide

No contributing guide indexed for this repository

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 at the Deployment Plan page and trace how the selected deployment region is passed into the Location dropdown after the deployment plan is generated. Reproduce the intermittent case with East US 2 and verify that the dropdown retains the selected region and does not treat the unchanged location as an update requiring another approval.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, typescript, vscode
Domain
cloud, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.