Support uninstrumented peer visualization for parameters, connection strings, and GitHub models resources

[davidfowl]

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

In Aspire 9.3, the dashboard gained support for visualizing outgoing calls to resources that do not emit their own telemetry, such as databases, caches, and infrastructure lacking built-in tracing. However, parameters, connection strings, and GitHub models resources are not yet included in this mechanism. As a result, outgoing calls from these resource types to uninstrumented peers do not appear as referenced peers in the trace timeline.

Describe the solution you'd like

Extend the uninstrumented peer visualization mechanism to cover parameters, connection strings, and GitHub models resources. Specifically:

• Outgoing calls from these resource types to uninstrumented peers should be displayed in the Traces dashboard.
• No instrumentation changes should be required for users to benefit from this feature.
• The trace UI and experience should match the behavior for currently supported resource types.

Additional context

This enhancement will provide full visibility over dependency chains, regardless of resource instrumentation, and ensure a consistent tracing experience across all modeled resource types. It will also improve debugging and dependency analysis for applications relying on parameters, connection strings, and GitHub models.

Original context:

Uninstrumented resources now appear in Traces
In 9.3, the dashboard can now visualize outgoing calls to resources that don't emit their own telemetry—such as databases, caches, and other infrastructure components that lack built-in tracing. ...

We made this work for the new external resources and we need to do the same for parameters, connection strings and github models.

We need to update the logic in https://github.com/dotnet/aspire/blob/da81496b05712535a784f5cf8218b627e958eef0/src/Aspire.Dashboard/Model/ResourceOutgoingPeerResolver.cs to handle some known properties in resources that have urls or endpoints:

resource.connectionString

aspire/src/Shared/Model/KnownProperties.cs

Line 28 in da81496

public const string ConnectionString = "resource.connectionString";

Value

aspire/src/Shared/Model/KnownProperties.cs

Line 59 in da81496

public const string Value = "Value";