Description

Aspire.Hosting.Testing currently adds a random suffix to resource names to reduce the chance of clashes when running tests in parallel. This is no longer necessary, as @karolz-ms points out, since DCP includes its own distinguisher. This PR disables resource name suffix randomization.

Users can still randomize resource name suffixes themselves by passing a random suffix to DistributedApplicationTestingBuilder like so:

var appHost = await DistributedApplicationTestingBuilder.CreateAsync<Projects.TestingAppHost1_AppHost>([$"DcpPublisher:ResourceNameSuffix={Random.Shared.Next():x}"]);
await using var app = await appHost.BuildAsync();
await app.StartAsync();

For context, see: #6891 (comment)

Fixes #6891
Fixes #6850

I verified that this addresses the above issue by running the Aspire.Hosting.Testing.Tests suite locally. I don't feel we need a specific unit test for this behavior at this time.

Before this change:

After this change:

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Is this introducing a breaking change?
      • Yes
        • Link to aspire-docs issue (please use this breaking-change template):
      • No
        • Link to aspire-docs issue (please use this doc-idea template):
  • No