microsoft / microsoft/vscode-azureresourcegroups
[CoR] Deployment workflow advances to Azure context collection before plan review/approval and UI remains in "Preparing deployment"
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 78
- Forks
- 55
- Avg merge
- 16h 49m
- Merged PRs (30d)
- 139
Description
OS: Win11 x64
Build Version: 0.12.7-alpha.0
Regression: Not a regression
Repro Steps:
- Create an Azure Project and complete Project Creation and Local Development.
- Enter the Deployment stage.
- Wait for deployment-plan.md to be generated.
- Observe the Deployment UI and Copilot chat panel.
Expect:
The deployment workflow should remain at the plan review stage after deployment-plan.md is generated.
Users should review and approve the deployment plan before Azure deployment questions are presented.
The Deployment UI and Copilot workflow state should remain synchronized.
Actual:
The Deployment page remains in "Preparing deployment..." state.
Copilot chat reports:
- "The plan-only gate passed"
- "Asking 5 questions (Subscription, Location, Classification, Scale, Budget)"
Copilot immediately starts collecting Azure deployment information, beginning with:
- "Which Azure subscription name or ID should this deployment target?"
The workflow proceeds to Azure context collection even though the deployment plan has not been explicitly reviewed or approved.
More Info:
- This issue is intermittent and does not reproduce consistently.
- In some runs, the deployment workflow progresses normally, while in others the workflow advances to Azure context collection before the deployment plan review/approval step is completed.
- The issue may be related to intermittent deployment state synchronization or state machine transition failures.
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 in the Deployment workflow after deployment-plan.md is generated, tracing the transition from plan review to Azure context collection and comparing the Deployment UI with the Copilot workflow state. Reproduce the intermittent behavior across runs. Done when Azure questions wait for explicit plan approval and the UI and Copilot state remain synchronized.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript, vscode
- Domain
- cloud, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100