[docs] Add troubleshooting note for DevTunnel URL publication fix - #1570
Karol Zadora-Przylecki (karolz-ms) merged 14 commits into
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Frontend HTML artifact readyThe latest frontend build uploaded the This comment updates automatically when a new frontend build artifact is uploaded. |
David Pine (IEvangelist)
left a comment
There was a problem hiding this comment.
🤖 Automated docs-accuracy review — PR #1570
Source of truth: microsoft/aspire@main @ 1cdf7d17248ae78ee018abbc314f772ace5e624d — confirmed to contain the source PR microsoft/aspire#19590 (f7073a8f2d, "Fix DevTunnel endpoint URL publication").
⚠️ Branch mismatch (non-blocking). This PR targetsrelease/13.6, which does not exist inmicrosoft/aspire. Verified againstmain(contains the fix). Note the version landscape below — it's directly relevant to this PR's wording.
Phase A — claims: 4 non-narrative claims → 1 verified · 3 verified-with-nuance · 0 contradicted · 0 unverifiable.
Phase B — doc-tester: exercised /integrations/devtools/dev-tunnels/ → HTTP 200, 0 console errors/warnings; Troubleshooting/See-also insertion region renders; the addition is plain H4 + prose with no new components or links. Knowledge gap: the local build predates this PR.
Verdict: 🟡 COMMENT
The fix mechanism is accurately documented and fully verified. The only thing worth flagging is the version framing — see below. No contradictions, no Phase B critical issues; nothing blocking.
Phase A — Claim verification
⚠️ Nuance worth flagging — the "13.5 bug / fixed in 13.6" version framing is imprecise
The fix mechanism is correct, but the version attribution doesn't quite match the source:
- Latest GA is
v13.4.6— there are no13.5or13.6release tags yet (both are unreleased/preview). - The regression cause (proxyless endpoint allocator, microsoft/aspire#17924) is not present in
v13.4.6, so no shipped release ever exhibited the bug — it lived only in untaggedmain/ preview builds between #17924 and the fix. release/13.5is13.5.0-preview.1and already contains the fix (backported). It's inmain(milestone 13.6) and the 13.5 line.- Consequence: "In Aspire 13.5 … could reach Running/Healthy without a URL" and "update to Aspire 13.6 or later" understate reality — a 13.5 (preview.1+) build already includes the fix, and the bug never shipped in a GA release. The guidance isn't harmful (13.6 does contain the fix), just narrower than the source shows. Consider softening to something like "fixed in Aspire 13.6 (and 13.5 servicing builds)" once versions firm up.
This is non-blocking; the reader still gets correct, actionable advice.
Claim verdicts (4) with evidence, against microsoft/aspire@1cdf7d17
| # | Type | Claim (diff line) | Verdict & evidence |
|---|---|---|---|
| N2 | api-behavior | "dev tunnel endpoints stay unallocated until the integration publishes the real tunnel endpoint" (L306-307) | verified — DcpExecutor.cs NeedsPublicPort (fix f7073a8f2d, ~L837): now (resource is IComputeResource || resource.IsContainer()) && !endpoint.IsProxied && !TryGetEffectiveFixedPublicPort(...) — comment "integration-owned endpoints publish their own addresses." Test DcpExecutorTests.ProxylessPortAllocatorOnlyAllocatesPortsForDcpWorkloads (added): with AddDevTunnel("tunnel"), asserts the tunnel endpoint's Port, TargetPort, and AllocatedEndpoint are all null; the compute endpoint still gets a port. |
| N1 | api-behavior | "In Aspire 13.5, dev tunnel resources could reach Running/Healthy … without ever publishing a public URL" (L304-305) | verified-with-nuance — the pre-fix allocator did assign a port to integration-owned endpoints (the real root cause), so the broken behavior is genuine; but the "13.5" attribution is imprecise (see above): no GA 13.5, and release/13.5 already has the fix. The exact dashboard-state symptom isn't asserted in the fix's unit tests. |
| N3 | api-behavior | "the dashboard and MCP resource snapshots now show the tunnel URL as expected" (L307-308) | verified-with-nuance — correct downstream consequence of N2 (both dashboard and MCP read the resource snapshot that now carries the real endpoint URL); the specific dashboard/MCP surfaces aren't directly asserted in the fix's changed tests. |
| N4 | package-or-version | "fixed in Aspire 13.6" / "update to Aspire 13.6 or later" (L305-306, L309) | verified-with-nuance — fix is in main (milestone 13.6) ✓, and backported to release/13.5 (13.5.0-preview.1); with no 13.5/13.6 GA (latest v13.4.6), "13.6 or later" is narrower than the source shows. |
Phase B — doc-tester report
Focus: new "Dashboard doesn't show a tunnel URL" troubleshooting subsection · Route: http://localhost:51482/integrations/devtools/dev-tunnels/#troubleshooting · Tester: doc-tester skill (blind-user; no source reading).
| Category | Passed | Failed | Warnings |
|---|---|---|---|
| Content accuracy (rendered) | n/a | 0 | 0 |
| Components / rendering | 2 | 0 | 0 |
| Links | 0 new | 0 | 0 |
Critical issues: none. Warnings: none.
Passed checks
- Page health:
GET /integrations/devtools/dev-tunnels/→ 200, title "Dev Tunnels integration | Aspire". 0 console errors, 0 warnings. - Troubleshooting section renders: H3 "Troubleshooting" (
#troubleshooting) with existing H4 subsections ("Authentication required", the "Verify that:" list). The new H4 subsection follows the same pattern → renders. - Insertion region intact: new subsection sits between the "Verify that:" list and the "## See also" H2 (
#see-also); both anchors resolve. - No new components or links: the diff adds a plain H4 + one paragraph only — zero link/component risk.
- The page already states "The tunnel URLs are shown in the Aspire dashboard," the documented behavior the fix restores — consistent framing.
Knowledge gap — running build predates PR #1570
- The local frontend doesn't contain this change (sibling worktree predating the PR), so the literal new subsection couldn't be rendered. I validated page health, the Troubleshooting/See-also anchors, and that the H4+paragraph pattern renders here, with no new links/components. Plain-prose addition ⇒ render failure effectively impossible.
Automated review · Phase A read microsoft/aspire@main 1cdf7d17 (source of truth = upstream, not the local origin fork) · Phase B via doc-tester (blind-user, Playwright).
Adam Ratzman (adamint)
left a comment
There was a problem hiding this comment.
No issues from this review.
Alistair Matthews (alistairmatthews)
left a comment
There was a problem hiding this comment.
A few minor changes. Otherwise it's good to go.
…ps (#1780) ## Summary <!-- Describe what this pull request changes and why. --> Reconcile the 13.6 wiki audit and **all 25 open `docs-from-code` proposals targeting `release/13.6`** against the actual release source. Add missing canonical guidance rather than putting all coverage in What's new. This is a new, isolated feature PR into `release/13.6`; it does not update the release rollup #1599, merge or close another proposal, or push directly to a release branch. **Draft with explicit remaining packaging/validation gates:** the six REPL walkthroughs are source-verified, but current publicly available 13.6 packages do not contain the late `WithRepl` exports. Generated API catalogs have deliberately not been fabricated or refreshed from 14.x. See the open checklist below. ### Evidence baseline - Documentation base: `717442f6666948bcf77f3d704dc2dadf7c080ec2`. - Product source of truth: [`microsoft/aspire@e8fd6fbb954f50ccd2e66479538392f65e13e71d`](https://github.com/microsoft/aspire/tree/e8fd6fbb954f50ccd2e66479538392f65e13e71d), current `release/13.6` at audit time. Source was read from that Git object, not the stale source working directory. - [13.6 wiki](https://github.com/microsoft/aspire/wiki/13.6-Change-log) snapshot `8e01a371d4f16a1306e48174d4cf1fdeca714348`, whose cutoff is product PR 20511. Later backports 20541/20546/20548 are included here. - Proposal base branches alone were **not** used as proof of release membership. Direct ancestry and known release backports were checked. Four fallback-targeted proposals are excluded below. - Wiki link corrections: its REPL link #1752 actually covers Sandboxes; the REPL proposal is #1740. Its AOT link #1714 covers PFX certificates, not AOT. ### Complete audit-gap checklist Checked items mean documentation coverage is implemented, not that cloud deployment or every product runtime scenario was executed. - [x] **1. Dotnet API graduation:** correct removal to **13.6**, not 14.0, in What's new, both Dotnet guides, and the diagnostic page; preserve the prerelease package caveat. This applies to core `AddDotnetProject`, `DotnetProjectResource`, and related `WithBuildEnvironment` overloads, not all uses of the diagnostic. Source: microsoft/aspire#20496. - [x] **2. Sandboxes:** remove obsolete API suppressions in the article and deployment guide while preserving Azure service preview/access and prerelease package limitations. Source: microsoft/aspire#20483. - [x] **3. Docked REPL documentation:** all six PostgreSQL/MySQL/MongoDB/SQL Server/Redis/Valkey guides plus the article now cover opt-in `WithRepl`/`withRepl`, run-only availability, actual client privileges, credential handling, and explicit exit versus closing a viewer. Source: microsoft/aspire#20419, backport of microsoft/aspire#20231. Package-backed checks remain open below. - [x] **4. Terminal CLI flag:** update current 13.6 article, `with-terminal`, and all three terminal command references. Preserve `terminals.v1` and experimental hosting API distinctions. Current configuration/schema data had no flag entry to remove; historical 13.5 notes remain historical. Source: microsoft/aspire#20548. - [x] **5. First-party Rust:** rewrite both canonical Rust guides around `Aspire.Hosting.Rust`; document Cargo versus application arguments, typed targets, debugging, generated Dockerfiles, workspace context, ABI constraints, and Toolkit migration. Bacon remains explicitly Toolkit-only. Add exact first-party package mapping. Source: microsoft/aspire#18906 and current Rust README. - [x] **6. Agent setup:** align command reference, skills guide, AI-agent guide, and article on MCP opt-in, `--mcp`, chained/non-interactive behavior, seven-skill catalog, Project v2 migration, and Copilot app detection. Also fix stale default-selection text: all applicable bundle skills are preselected; companion tools remain opt-in. Sources: microsoft/aspire#19893, microsoft/aspire#20405, microsoft/aspire#19820. - [x] **7. Deno AppHost runtime:** document Deno 2+ detection, commands, permissions, native watch/type checking, doctor, and `DENO_CERT`, separately from Deno guest hosting. Source: microsoft/aspire#18627, distinct from microsoft/aspire#18628. - [x] **8. Native AOT / Fluent UI v5:** concise article, dashboard exploration, and standalone guidance; automatic packaged-dashboard selection, no invented performance figures. Source: microsoft/aspire#19565 and release packaging sources. - [x] **9. NuGet:** document bundled in-process operations, credential providers, non-interactive authentication, and realistic troubleshooting. Correct the proposal's `dotnet nuget locals` authentication advice: cache commands do not authenticate a feed. Source: microsoft/aspire#20391. - [x] **10. Multithreaded builds:** article and coordinated-build guide explain `-mt`, SDK detection, distinct project/file-based SDK floors, and fallback. Source: microsoft/aspire#20441. - [x] **11. Radius:** add a real deployment guide with C#/TypeScript setup, recipe-backed connections versus local endpoints, per-resource credential behavior, unauthenticated Redis limitation, secret exposure boundaries, and actionable runtime diagnostics 070–091. Wire navigation and exact package mapping. Source: microsoft/aspire#19555 and release README. - [x] **12. Connection aliases:** replace contradictory no-encoding guidance, retain composed logical-key-first lookup and portable-target behavior, explain collision detection and custom-publisher metadata. Source: microsoft/aspire#19729. - [x] **13. Connector Namespace / Toolbox / provisioning:** add Connector Namespace walkthrough, security/consent/revocation limits and mapping/sidebar; add Foundry Toolbox walkthrough, connection properties, roles, index prerequisites, approval enforcement boundaries, immutable versions, and existing-resource behavior. Extend existing Azure provisioning guide without a duplicate page. Sources: microsoft/aspire#19024, microsoft/aspire#17742, microsoft/aspire#20131. - [x] **14. Remaining high-impact items:** article covers opt-in manifest-aware DNX and new-template CLI bundling (existing SDK guides retained), migration skill and Copilot app detection; canonical inline `CsiVolumeSourceV1`/`VolumeV1.Csi` example, management links, Cosmos vNext telemetry, and AI Inference `GetModelInfoAsync`/`/info` health checks with `DisableHealthChecks`. No Azure OpenAI health-check claim. Sources: microsoft/aspire#19310, microsoft/aspire#19076, microsoft/aspire#19826, microsoft/aspire#20070, microsoft/aspire#15671, microsoft/aspire#15969. - [x] **15. All 25 proposal dispositions:** listed below, including newer dashboard backports and four exclusions. Existing Sandbox inference coverage is retained rather than copied from a stale draft. - [ ] **16. Refresh generated API/catalog/Twoslash data from an official post-backport 13.6 build.** Existing `26473.12`/`a11eca96` data remains untouched. The newest public `dotnet9` feed package checked, `13.6.0-preview.1.26474.10` at `43496a2a306c81c862c947b11b4f4e5494b6fe08`, still has no Redis `WithRepl` in its actual package XML. Do not use 14.x, hand-edit declarations, or attribute source changes to older binaries. - [ ] **Validate the six REPL examples against that actual post-backport SDK and running clients.** Their new TypeScript fences are plain TypeScript, not annotated with unsupported Twoslash data. No existing diagnostics are allowlisted or suppressed; no generated API exports are fabricated. Enable Twoslash when the genuine catalog catches up. ### All 25 open proposal dispositions and provenance Text is selectively adapted from these proposals, not merged wholesale. #1778 and #1748 are authored by @sebastienros; the other proposals are authored by the Aspire repo bot. The table credits the associated product-change authors where supplied by the proposals. Existing PRs remain open and unchanged. | Docs PR | Release source / credited product author | Disposition | | --- | --- | --- | | #1778 | microsoft/aspire#19729 — @sebastienros | **Adopted:** canonical connection-string alias correction, including logical-first resolution and migration. | | #1771 | microsoft/aspire#20481 — @sebastienros | **Excluded:** flat polyglot feature keys are not in the audited release tip; no verified backport. Preserve release key names. | | #1770 | microsoft/aspire#20525 → microsoft/aspire#20548 — @mitchdenny | **Corrected/adopted:** command guides plus the still-current 13.6 article, which the proposal incorrectly treats as historical. | | #1769 | microsoft/aspire#20416 — @JamesNK | **Excluded:** brand hover change has no verified 13.6 membership/backport. | | #1768 | microsoft/aspire#20523 → microsoft/aspire#20546 — @JamesNK | **Adopted:** run pin/unpin preserves selector and current selection. | | #1766 | microsoft/aspire#20537 → microsoft/aspire#20541 — @mitchdenny | **Adopted:** terminal dock empty state. | | #1761 | microsoft/aspire#20490 → microsoft/aspire#20496 — @eerhardt | **Corrected:** graduation is 13.6, package remains prerelease, Blazor-specific exception retained. | | #1760 | microsoft/aspire#20436 — @eerhardt | **Excluded:** CLI net11/tools-any retarget is not in the audited release; no fallback-base inference. | | #1748 | microsoft/aspire#20131 — @sebastienros | **Adopted:** extend existing provisioning guide with service-specific models/lookups and projection limits. | | #1744 | microsoft/aspire#20337 → microsoft/aspire#20441 — @karolz-ms | **Adopted:** precise SDK-conditional multithreaded build coverage. | | #1740 | microsoft/aspire#20231 → microsoft/aspire#20419 — @mitchdenny | **Adapted:** all six guides; TypeScript-first tabs, source-verified lifecycle/security. Actual post-backport SDK/runtime gate is open above. | | #1738 | microsoft/aspire#20158 → microsoft/aspire#20405 — @karolz-ms | **Partly already covered / completed:** existing seven-skill catalog retained; add project migration guidance and correct command catalog/defaults. Do not misclassify the bundled skill as a companion tool. | | #1735 | microsoft/aspire#20334 — @karolz-ms | **Excluded:** enhanced startup errors are not in the audited release; no verified backport. | | #1731 | microsoft/aspire#19847 → microsoft/aspire#20391 — @eerhardt | **Corrected/adopted:** in-process NuGet and real authenticated-restore troubleshooting, not cache-command authentication. | | #1719 | microsoft/aspire#20299 → microsoft/aspire#20407 — @JamesNK | **Corrected/adopted:** cookie naming/scoping; identical names can collide but do not guarantee cross-dashboard cookie decryptability or shared sign-in. | | #1664 | microsoft/aspire#20011 — @maddymontaquila | **Adopted:** concise Azure environment icon release note. | | #1628 | microsoft/aspire#17742 — @davidfowl | **Adapted/expanded:** canonical Toolbox examples, consumer contract, role/index prerequisites, approval/security and concurrency limits. | | #1623 | microsoft/aspire#19810 — @mitchdenny | **Already covered:** current Sandbox guide/article already describe compute inference, explicit selection and external endpoints. Preserve that guidance while removing obsolete suppressions. | | #1620 | microsoft/aspire#19243 — @sebastienros | **Adapted:** AKS credential-before-Helm cleanup and destructive-operation warning; omit misleading ambient-context workaround. | | #1614 | microsoft/aspire#19870 — @sebastienros | **Adopted:** typed callback handle behavior in extension authoring and article. | | #1574 | microsoft/aspire#19430 — @mitchdenny | **Adapted:** canonical hostname inheritance, explicit-host precedence, catch-all default backend. | | #1570 | microsoft/aspire#19590 — @karolz-ms | **Adopted:** Dev Tunnel URL regression troubleshooting. | | #1565 | microsoft/aspire#19429 — @mitchdenny | **Corrected/adopted:** Helm embedded parameters with real `refExpr` and `addParameter(name, { value })`, not stringifying a handle or using an invalid actual-SDK overload. | | #1564 | microsoft/aspire#19026 — @karolz-ms | **Corrected/adopted:** C#/TypeScript Dotnet gateway walkthrough. Retain both experimental diagnostics; remove obsolete run-only restriction after microsoft/aspire#19997 publishing support. Avoid imported ambiguous API reference. | | #1499 | microsoft/aspire#19248 — @IEvangelist | **Adopted:** describe exact secret-value redaction and embedded-secret limit; release article already covered the fix. | ### Important source-verified corrections to proposals / earlier audit assumptions - [`BlazorGatewayExtensions.cs`](https://github.com/microsoft/aspire/blob/e8fd6fbb954f50ccd2e66479538392f65e13e71d/src/Aspire.Hosting.Blazor/BlazorGatewayExtensions.cs): `AddDotnetProjectBlazorGateway` and the Dotnet `WithBlazorClientApp` overload still carry `ASPIREDOTNETPROJECT001`; the class carries `ASPIREBLAZOR001`. They share `WithBlazorClientAppCore`/`WithBlazorApp` and the publish-companion path. Thus neither blanket diagnostic retirement nor the proposal's old run-only claim is correct. - [`SkillDefinition.cs`](https://github.com/microsoft/aspire/blob/e8fd6fbb954f50ccd2e66479538392f65e13e71d/src/Aspire.Cli/Agents/SkillDefinition.cs) sets bundled skills' `IsDefault=true`; [`AgentInitCommand.cs`](https://github.com/microsoft/aspire/blob/e8fd6fbb954f50ccd2e66479538392f65e13e71d/src/Aspire.Cli/Commands/AgentInitCommand.cs) selects the applicable catalog defaults for both flows. MCP has its own standalone-only binding. - [`TypeScriptAppHostToolchainResolver.cs`](https://github.com/microsoft/aspire/blob/e8fd6fbb954f50ccd2e66479538392f65e13e71d/src/Aspire.Cli/Projects/TypeScriptAppHostToolchainResolver.cs) is the source for Deno flags and certificate variable; guest Deno hosting is separate. - [`Radius README`](https://github.com/microsoft/aspire/blob/e8fd6fbb954f50ccd2e66479538392f65e13e71d/src/Aspire.Hosting.Radius/README.md) supplies the resource-specific credential rules and publish diagnostics, not assumptions about local endpoints. ## Third-party links and affiliations <!-- List third-party links and disclose material affiliations. --> Links point to official Microsoft Learn, VS Code Marketplace debugger extensions, Rust/Cargo/Bacon documentation, Radius documentation, and source repositories. No sponsorship, commercial endorsement, or affiliation claim is introduced. Maintainers should supply any personal affiliation disclosure required by policy; automation has not inferred one. ## Validation <!-- List the checks you ran or explain why validation isn't needed. --> - **97 passing focused unit checks** across API-reference authoring/rendering, Twoslash blocks, file-tree formatting, CLI configuration schema, SEO lengths, and resource catalog. - **82 passing structured-data checks**, including exact integration mapping uniqueness and page resolution. - **11 C# samples compile**, zero warnings/errors, using genuine `13.6.0-preview.1.26473.12` packages. Scope: Rust, Connector Namespace, Radius, Toolbox, inline CSI, Helm, Blazor gateway, and provisioning. `Projects.Api/Worker/Client` use compile-only `IProjectMetadata` stand-ins; no claim of running those apps or provisioning cloud resources. - **10 TypeScript samples pass `tsc`** under `strict`, `NodeNext`, and `ES2022` against three **unmodified actual SDK files**, not just the site's declaration bundle. The fixture uses the exact `e8fd6fbb` release `AtsCapabilityScanner` and genuine `26473.12` TypeSystem/code-generator/integration binaries, whose informational source is `a11eca96`. This is an isolated local generation fixture, **not** a claim that official CLI generation or a new packaged release was tested. An attempted restore with the older handed-off local CLI could not discover an AppHost server; the bounded direct generator fixture was used instead. - The SDK scan is **not globally warning-free**: it reports a Radius `withContainerImage` collision on `CSharpAppResource` and an App Configuration `createRoleAssignment` overload collision. None of the compiled examples calls those colliding methods; the warnings are retained in evidence, not suppressed, and no generated declarations were edited. - Browser: Connector Namespace, Radius, both Rust pages, Foundry hosting, and What's new return **HTTP 200**, correct headings, and no rendered Twoslash errors. New guide/article page-local anchors and the cross-page Blazor anchor resolve. Connector/Radius mobile layouts have no horizontal overflow; Connector language-tab interaction works. Standalone Astro preview emits expected `/api/live` 404s because StaticHost is not running. - `git diff --check` passes. No production `pnpm build`, cloud deployment, REPL runtime session, full product suite, or blanket validation of every pre-existing example was performed. - Generated C#/TypeScript API data, declaration bundles, integration catalogs, image catalogs, and contributor data are unchanged. Only the authored package-to-guide mapping is updated. **Before merging:** complete the two packaging/REPL checkboxes above, inspect CI, and obtain human review. This PR intentionally does not close or merge the source documentation proposals. --------- Co-authored-by: David Pine <7679720+IEvangelist@users.noreply.github.com> Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Alistair Matthews <alistairwebdojo@live.com>
Co-authored-by: Alistair Matthews <alistairwebdojo@live.com>
Co-authored-by: Alistair Matthews <alistairwebdojo@live.com>
Co-authored-by: Alistair Matthews <alistairwebdojo@live.com>
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
Remove duplicate bullets and confirm the documented version-specific behavior.
Review effort: Lite
Findings: 1
Open (1)
What changed in this PR
Adds troubleshooting guidance for a DevTunnel URL publication regression in Aspire 13.5 and its fix in 13.6.
Changes:
- Documents the missing tunnel URL symptom and upgrade guidance.
- Updates DevTunnel introductory bullets, with duplicate entries requiring removal.
| File | Summary |
|---|---|
src/frontend/src/content/docs/integrations/devtools/dev-tunnels.mdx |
Adds troubleshooting guidance and modifies introductory bullets; version-specific claims require confirmation. |
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| - Sharing a running local service (for example, a Web API) with teammates, mobile devices, or webhooks. | ||
| - Testing incoming callbacks from external SaaS systems (GitHub / Stripe / etc.) without deploying. | ||
| - Quickly publishing a temporary, TLS-terminated endpoint during development. |
Co-authored-by: Alistair Matthews <alistairwebdojo@live.com>
Co-authored-by: Alistair Matthews <alistairwebdojo@live.com>
Co-authored-by: Alistair Matthews <alistairwebdojo@live.com>
Co-authored-by: Alistair Matthews <alistairwebdojo@live.com>
Co-authored-by: Alistair Matthews <alistairwebdojo@live.com>
Co-authored-by: Alistair Matthews <alistairwebdojo@live.com>
Co-authored-by: Alistair Matthews <alistairwebdojo@live.com>
Co-authored-by: Alistair Matthews <alistairwebdojo@live.com>
|
Copilot resolve the merge conflicts in this pull request |
…-32758524812-1-79dab64499172993 # Conflicts: # src/frontend/src/content/docs/integrations/devtools/dev-tunnels.mdx Co-authored-by: karolz-ms <15271049+karolz-ms@users.noreply.github.com>
Resolved the merge conflict and merged |
fe34a54
into
release/13.6

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.