microsoft / microsoft/vscode-azurecontainerapps
External Ingress incorrectly reported
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 42
- Forks
- 21
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 2
Description
OS: All
Build Version: 20250709.1
Regression: Not a Regression
Repro Steps:
Configure Container App Environment to disable public network access. Configure with VNet, Subnet & internal VIP.
Configure Container App to allow ingress, Limited to VNet. Configure IP Security Restrictions Mode to Allow all traffic.
Expect:
The Container App should show Only allowing traffic within your vNet under Configurations -> Ingress -> External.
Actual:
The Container App shows Accepting traffic from anywhere under Configurations -> Ingress -> External.
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 the VS Code Azure Container Apps extension using an internal-VIP environment, VNet-limited ingress, and Allow all traffic IP restrictions. Compare the External ingress text with the expected “Only allowing traffic within your vNet” result; the work is done when that configuration is no longer shown as “Accepting traffic from anywhere.”
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript
- Domain
- cloud, devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100