microsoft / microsoft/vscode-azurecontainerapps
The replicas value doesn't auto refresh in the "xxx_Scaling.json" file after editing scaling range
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 42
- Forks
- 21
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 2
Description
Environment: VSCode.dev
Container Apps Build Version: v0.4.2-alpha.0
Resource Group Build Version: v0.6.3-alpha.0
Repro Steps:
- Create a container app and expand it.
- Right click "Scaling" node -> Edit Scaling Range… -> Set the range -> Enter.
- Right click "Scaling" node -> View Properties.
- Check whether the replicas value auto refreshes in the
xxx_Scaling.jsonfile.
Expect:
The replicas value auto refreshes in the xxx_Scaling.json file.
Actual:
The replicas value doesn't auto refresh in the xxx_Scaling.json file.
More Info:
- This issue also reproduces after executing "Add Scale Rule..." action.
- This issue also reproduces after executing "Switch Ingress Visibility.../Edit Target Port...".
- Reload VSCode can fix this issue.
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 issue in VSCode.dev using the Scaling node, then inspect how Edit Scaling Range, Add Scale Rule, Switch Ingress Visibility, and Edit Target Port update the xxx_Scaling.json properties view. Confirm that the replicas and related values refresh immediately after each action without reloading VS Code.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100