microsoft / microsoft/vscode-azurecontainerapps
Logs for selected resource context appear prematurely during Container App creation flow
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 42
- Forks
- 21
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 2
Description
OS: Win 11 x64
Build Version: 20260608.1
Regression: Not a Regression
Repro Steps:
- Run Create Container App command.
- Select an existing Container App Environment.
- Observe the output logs before reaching the step to enter the container app name.
Expect:
Resource-related logs should be shown after all required inputs are collected or be clearly associated with the current step.
Actual:
The following logs are displayed immediately after environment selection and before entering the app name:
More Info:
May mislead users into thinking the creation process has already started before all required inputs are provided.
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 Create Container App command flow and reproduce the transition after selecting an existing Container App Environment. Trace where the resource-related logs are emitted before the app name step, then verify that they appear only after required inputs are collected or are clearly tied to the current step.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript
- Domain
- cloud, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100