Remove fake passwords from ExpressionResolverTests test data

[Copilot]

Test data in ExpressionResolverTests.cs contained fake passwords (Password=xxx;) that trigger credential scanning tools, though the tests validate hostname resolution, not authentication.

Changes

• Removed Password=xxx; from 6 InlineData attributes on HostUrlPropertyGetsResolved test method (lines 156-161)

The test validates that localhost/127.0.0.1/[::1] gets replaced with aspire.dev.internal in connection strings when targeting containers. Password fields are irrelevant to this validation.

Before:

[InlineData(false, "Server=localhost,1433;User ID=sa;Password=xxx;Database=yyy", "Server=localhost,1433;User ID=sa;Password=xxx;Database=yyy")]

After:

[InlineData(false, "Server=localhost,1433;User ID=sa;Database=yyy", "Server=localhost,1433;User ID=sa;Database=yyy")]

Original prompt

In ExpressionResolverTests.cs file some of the InlineData attributes on HostUrlPropertyGetsResolved contain a fake password (Password=xxx;). I think this is unnecessary and causes problems with tools that are scanning the code for credentials. Can you prepare a PR that removes these fake passwords from the test data? Leave everything else as-is.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[github-actions]

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 12525

Or

• Run remotely in PowerShell:

iex "& { $(irm https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 12525"

[Copilot]

Pull Request Overview

This PR removes password information from SQL Server connection string test data. The changes eliminate the Password=xxx; parameter from six test cases to avoid exposing sensitive credential patterns in test code.

Key Changes

• Removed Password=xxx; from SQL Server connection string test data across all scenarios (localhost, 127.0.0.1, and [::1])
• Maintains test coverage for host URL resolution in both container and non-container contexts

[karolz-ms]

#12521 will take care of this