Is there an existing issue for this?
Describe the bug
When ApplicationName is missing or whitespace, DashboardRunStore falls back to the fixed name Aspire. Unrelated standalone Dashboard sessions using --persistence Resume and the same data root therefore reuse the same database.
The documentation demonstrates supplying a stable application name, but the CLI neither requires one nor warns that omission selects a shared per-user identity.
Expected Behavior
Resume should require a stable application name, derive a context-specific identity, or clearly warn that the default identity will reuse data across standalone sessions.
Steps To Reproduce
- From one working directory, run
aspire dashboard run --persistence Resume with an isolated data root.
- Stop the Dashboard.
- Repeat from an unrelated working directory with the same data root.
- Both sessions use
Aspire-6b6645454dc0e896/dashboard.db.
Exceptions (if any)
N/A
Aspire doctor output
Aspire CLI 13.6.0-pr.18924.g5ee63941
Ubuntu 24.04.3
Anything else?
Related to #18924. Source: src/Aspire.Dashboard/ServiceClient/DashboardRunStore.cs:105,538-545. The behavior remains on current main.
Is there an existing issue for this?
Describe the bug
When
ApplicationNameis missing or whitespace,DashboardRunStorefalls back to the fixed nameAspire. Unrelated standalone Dashboard sessions using--persistence Resumeand the same data root therefore reuse the same database.The documentation demonstrates supplying a stable application name, but the CLI neither requires one nor warns that omission selects a shared per-user identity.
Expected Behavior
Resumeshould require a stable application name, derive a context-specific identity, or clearly warn that the default identity will reuse data across standalone sessions.Steps To Reproduce
aspire dashboard run --persistence Resumewith an isolated data root.Aspire-6b6645454dc0e896/dashboard.db.Exceptions (if any)
N/A
Aspire doctor output
Anything else?
Related to #18924. Source:
src/Aspire.Dashboard/ServiceClient/DashboardRunStore.cs:105,538-545. The behavior remains on currentmain.