Partially fix quarantined test: Update stale snapshot for DeployAsync_WithMultipleComputeEnvironments_Works

[Copilot]

Description

Quarantined test DeployAsync_WithMultipleComputeEnvironments_Works has two test cases. This PR fixes the step="diagnostics" case by updating the stale snapshot, but the step="deploy" case still fails with an ACR login issue. The test remains quarantined.

Root Cause Analysis:

• The step="diagnostics" case was failing due to an out-of-date snapshot file caused by recent pipeline changes (added validate-appservice-config-aas-env validation step, removed update-api-service-provisionable-resource step)
• The step="deploy" case has an unresolved functional bug where only one ACR registry login occurs (acaregistry.azurecr.io) when both registries should be logged into (acaregistry.azurecr.io and aasregistry.azurecr.io)

Changes:

• Updated AzureDeployerTests.DeployAsync_WithMultipleComputeEnvironments_Works_step=diagnostics.verified.txt to reflect current pipeline structure
• Kept [QuarantinedTest] attribute because the step="deploy" case still fails

Status:

• ✅ step="diagnostics" - Fixed by snapshot update
• ❌ step="deploy" - Still fails with ACR login issue (unresolved)

The underlying ACR login bug for the deploy case requires further investigation. Issue #13287 remains open.

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
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
  • No
• Does the change require an update in our Aspire docs?
  • Yes
  • No

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Failing test: Aspire.Hosting.Azure.Tests.AzureDeployerTests.DeployAsync_WithMultipleComputeEnvironments_Works</issue_title>
<issue_description>## Build Information
Build: https://github.com/dotnet/aspire/actions/runs/19852141316
Build error leg or test failing: Aspire.Hosting.Azure.Tests.AzureDeployerTests.DeployAsync_WithMultipleComputeEnvironments_Works
Pull request:

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": "",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Error Details

Assert.Contains() Failure: Filter not matched in collection
Collection: [Tuple ("acaregistry.azurecr.io", "00000000-0000-0000-0000-000000000000", "fake-refresh-token")]
at Aspire.Hosting.Azure.Tests.AzureDeployerTests.DeployAsync_WithMultipleComputeEnvironments_Works(String step) in /Users/runner/work/aspire/aspire/tests/Aspire.Hosting.Azure.Tests/AzureDeployerTests.cs:line 439
--- End of stack trace from previous location ---

Standard Output

| [2025-12-02T03:47:45] Aspire.Hosting.DistributedApplication Information: Aspire version: 13.1.0-ci
[CreateStep] pipeline-execution
| [2025-12-02T03:47:45] Aspire.Hosting.Cli.BackchannelService Debug: Backchannel socket path was not specified.
| [2025-12-02T03:47:45] Aspire.Hosting.Backchannel.AuxiliaryBackchannelService Debug: Starting auxiliary backchannel service on socket path: /Users/runner/.aspire/cli/backchannels/aux.sock.4cca56afeebea85c
| [2025-12-02T03:47:45] Aspire.Hosting.Backchannel.AuxiliaryBackchannelService Debug: Auxiliary backchannel listening on /Users/runner/.aspire/cli/backchannels/aux.sock.4cca56afeebea85c
[CreateStep] process-parameters
| [2025-12-02T03:47:45] Aspire.Hosting.ApplicationModel.ResourceNotificationService Debug: Resource cache-password/cache-password changed state: Running
| [2025-12-02T03:47:45] Aspire.Hosting.ApplicationModel.ResourceNotificationService Trace: Version: 1 Resource cache-password/cache-password update published: ResourceType = ParameterResource, CreationTimeStamp = (null), State = { Text = Running, Style = (null) }, IsHidden = False, HeathStatus = Healthy, ResourceReady = False, ExitCode = (null), Urls = {  }, EnvironmentVariables = {  }, Properties = { Value = jshEqAXbaasgV8H8jYQ4WF }, HealthReports = {  }, Commands = {  }
    [Information:process-parameters] 1 parameter values saved to deployment state.
| [2025-12-02T03:47:45] Aspire.Hosting.ParameterProcessor Information: 1 parameter values saved to deployment state.
[CreateStep] deploy-prereq
    [Information:deploy-prereq] Initializing deployment for environment 'Test'
| [2025-12-02T03:47:45] Aspire.Hosting.Publishing.PipelineExecutor Information: Initializing deployment for environment 'Test'
    [Information:deploy-prereq] Setting default deploy tag 'aspire-deploy-20251202034745' for compute resource(s).
| [2025-12-02T03:47:45] Aspire.Hosting.Publishing.PipelineExecutor Information: Setting default deploy tag 'aspire-deploy-20251202034745' for compute resource(s).
[CreateStep] validate-azure-login
  [CompleteStep:validate-azure-login] Azure CLI authentication validated successfully (State: Completed)
[CreateStep] create-provisioning-context
| [2025-12-02T03:47:45] Aspire.Hosting.Azure.Provisioning.Internal.PublishModeProvisioningContextProvider Debug: Azure provisioning options have been handled successfully.
    [Information:create-provisioning-context] Default subscription: Test Subscription (/subscriptions/12345678-1234-1234-1234-123456789012)
| [2025-12-02T03:47:45] Aspire.Hosting.Azure.Provisioning.Internal.PublishModeProvisioningContextProvider Information: Default subscription: Test Subscription (/subscriptions/12345678-1234-1234-1234-123456789012)
    [Information:create-provisioning-context] Tenant: 87654321-4321-4321-4321-210987654321
| [2025-12-02T03:47:45] Aspire.Hosting.Azure.Provisioning.Internal.PublishModeProvisioningContextProvider Information: Tenant: 87654321-4321-4321-4321-210987654321
    [Information:create-provisioning-context] Using existing resource group test-rg.
| [2025-12-02T03:47:45] Aspire.Hosting.Azure.Provisioning.Internal.PublishModeProvisioningContextProvider Information: Using existing resource group test-rg.
[CreateStep] provision-aca-env
    [CreateTask:provision-aca-env] Deploying **aca-env**
| [2025-12-02T03:47:45] Aspire.Hosting.ApplicationModel.ResourceNotificationService Debug: Resource aca-env/aca-env changed state: Starting
...

</details>



<!-- START COPILOT CODING AGENT SUFFIX -->

- Fixes dotnet/aspire#13287

<!-- START COPILOT CODING AGENT TIPS -->
---

✨ Let Copilot coding agent [set things up for you](https://github.com/dotnet/aspire/issues/new?title=✨+Set+up+Copilot+instructions&body=Configure%20instructions%20for%20this%20repository%20as%20documented%20in%20%5BBest%20practices%20for%20Copilot%20coding%20agent%20in%20your%20repository%5D%28https://gh.io/copilot-coding-agent-tips%29%2E%0A%0A%3COnboard%20this%20repo%3E&assignees=copilot) — coding agent works faster and does higher quality work when set up for your repo.

[radical]

@copilot do not remove the attribute though, since the step: "deploy" case still fails with a different error. but confirm that in any case. We should not close the corresponding issue either.

[Copilot]

Confirmed - the step: "deploy" case still fails with the same ACR login error. Only one registry (acaregistry.azurecr.io) is being logged into when both (acaregistry.azurecr.io and aasregistry.azurecr.io) are expected. Restored the quarantine attribute in commit 72b9063.

The snapshot update only fixed the step: "diagnostics" case. The underlying ACR login issue for the deploy case remains unresolved.

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• aka.ms
  • Triggering command: /usr/local/bin/bicep /usr/local/bin/bicep build /tmp/aspire-bicepRmj3AM/aca-env-acr.module.bicep --stdout (dns block)
  • Triggering command: /usr/local/bin/bicep /usr/local/bin/bicep build /tmp/aspire-bicepkqXMcm/storage.module.bicep --stdout (dns block)
  • Triggering command: /usr/local/bin/bicep /usr/local/bin/bicep build /tmp/aspire-bicepmPFBR5/aas-env-acr.module.bicep --stdout (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[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 -- 14551

Or

• Run remotely in PowerShell:

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

[Copilot]

Pull request overview

This PR partially fixes a quarantined test by updating a stale snapshot file that validates pipeline diagnostics output. The test DeployAsync_WithMultipleComputeEnvironments_Works has two test cases: one for step="diagnostics" (now fixed) and one for step="deploy" (still failing). The snapshot update reflects recent pipeline changes where a validation step was added and an update step was removed.

Changes:

• Updated the verified snapshot file to reflect current pipeline structure (removed update-api-service-provisionable-resource step, added validate-appservice-config-aas-env validation step)
• Test remains quarantined as the step="deploy" case still fails with an ACR login bug (only one registry is logged into instead of both)