microsoft / microsoft/vscode-azureresourcegroups
[CoR]No validation for invalid subscription input from chat during deployment planning
Nobody has claimed this yet.
- 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.7-alpha.0
Regression: Not a regression
Repro Steps:
- Start a deployment workflow
- When prompted for the Azure subscription in chat, enter an arbitrary invalid value (for example, "test-subscription")
- Continue through the deployment planning process
- Approve the deployment plan and proceed with deployment
Expect:
The workflow should validate the subscription input and reject invalid values
Actual:
The invalid subscription input is accepted and the workflow continues without any validation or error message.
More Info:
- After entering "test-subscription", the value appeared as the first option and selected value in the Subscription dropdown on the Deployment Plan page.
- During deployment, the workflow used the current Azure subscription (AzCode2605) instead of the value entered by the user.
- No validation message was shown and the workflow did not indicate that the entered subscription value was invalid.
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
Reproduce the deployment workflow and enter an invalid value such as "test-subscription" when chat requests the Azure subscription. Trace that value through the Deployment Plan page and deployment flow, then verify that invalid subscriptions are rejected with an error and cannot be used to continue deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript, vscode
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100