[docs] Add troubleshooting note for DevTunnel URL publication fix - #1570
Draft
aspire-repo-bot[bot] wants to merge 1 commit into
Draft
[docs] Add troubleshooting note for DevTunnel URL publication fix#1570aspire-repo-bot[bot] wants to merge 1 commit into
aspire-repo-bot[bot] wants to merge 1 commit into
Conversation
Co-authored-by: Copilot <[email protected]>
aspire-repo-bot
Bot
added
the
docs-from-code
14 tasks
Contributor
Author
Frontend HTML artifact readyThe latest frontend build uploaded the This comment updates automatically when a new frontend build artifact is uploaded. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents changes from microsoft/aspire#19590
@karolz-msTargeting
release/13.6based on the source PR milestone13.6.Why
microsoft/aspire#19590 fixes a regression where DevTunnel port resources could reach
Running/Healthyin the dashboard while never publishing their public tunnel URL. The proxyless endpoint allocator (introduced in #17924) was assigning a temporary localhost port to DevTunnel endpoints, which the DevTunnel integration mistakenly treated as a signal that the real endpoint had already been published. The fix limits automatic proxyless port allocation toIComputeResourceinstances and containers, leaving integration-owned endpoints (like DevTunnel ports) unallocated until the integration publishes the real endpoint.The dev tunnels docs already state that "tunnel URLs are shown in the Aspire dashboard," so this is a
bug_fix_restores_documented_behaviorcase — the regression was a discrepancy from documented behavior, not a new feature. Since users hit this specific issue on 13.5, I added a short troubleshooting entry so anyone still on 13.5 (or debugging the symptom) can find the explanation and the fix version.Changes
src/frontend/src/content/docs/integrations/devtools/dev-tunnels.mdx: added a new "Dashboard doesn't show a tunnel URL" troubleshooting subsection explaining the 13.5 regression and the 13.6 fix.No new pages were created; only the existing Troubleshooting section was extended.