[release/9.4] Support uninstrumented peer visualization for parameters, and resources with connection strings and github models - #10382
Merged
Dan Moseley (danmoseley) merged 17 commits intoJul 14, 2025
Conversation
…n strings, and GitHub models Co-authored-by: davidfowl <95136+davidfowl@users.noreply.github.com>
Co-authored-by: davidfowl <95136+davidfowl@users.noreply.github.com>
Co-authored-by: davidfowl <95136+davidfowl@users.noreply.github.com>
Co-authored-by: davidfowl <95136+davidfowl@users.noreply.github.com>
… string parsing Co-authored-by: davidfowl <95136+davidfowl@users.noreply.github.com>
…roved documentation Co-authored-by: davidfowl <95136+davidfowl@users.noreply.github.com>
…eUrlHostAndPort Co-authored-by: davidfowl <95136+davidfowl@users.noreply.github.com>
Co-authored-by: davidfowl <95136+davidfowl@users.noreply.github.com>
Co-authored-by: davidfowl <95136+davidfowl@users.noreply.github.com>
…implifying hostname validation Co-authored-by: davidfowl <95136+davidfowl@users.noreply.github.com>
…solution and state management
Co-authored-by: davidfowl <95136+davidfowl@users.noreply.github.com>
…ction Co-authored-by: JamesNK <303201+JamesNK@users.noreply.github.com>
…omputation on each peer resolution Co-authored-by: davidfowl <95136+davidfowl@users.noreply.github.com>
Co-authored-by: davidfowl <95136+davidfowl@users.noreply.github.com>
dotnet-policy-service
Bot
added
Re-opened Github-Action PR
and removed
Closed Github-Action PR
labels
Member
|
This broke the code mirror, see #10383 |
Member
Looking into this. |
David Fowler (davidfowl)
approved these changes
Jul 14, 2025
Dan Moseley (danmoseley)
approved these changes
Jul 14, 2025
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Backport of #10340 to release/9.4
/cc David Fowler (@davidfowl) Copilot
Customer Impact
This PR enables uninstrumented peer visualization for parameters and resources with connection strings and GitHub models in Aspire. Customers will now be able to visualize connections and resource dependencies more accurately, even when instrumentation is not present. This improves the observability and troubleshooting experience for complex applications relying on external resources.
Testing
The changes were validated through unit and integration tests covering the new visualization logic and resource handling. Manual verification was performed to ensure that resources with connection strings and GitHub models appear correctly in the visualization, both in instrumented and uninstrumented scenarios. Automated CI pipelines for the Aspire repo also passed successfully.
Risk
Risk is moderate. While the changes largely extend existing visualization logic, they touch core components responsible for resource detection and graph rendering. There is some risk of unintended side effects in visualizations for edge cases or previously unsupported resource types. However, the changes are isolated to visualization and do not impact resource creation or connection logic.
Regression?
This change is not expected to introduce regressions in existing scenarios. The visualization updates are additive and should not affect instrumented resources or existing connection logic. However, additional testing should be done if any custom visualizations or non-standard resource providers are in use.