Fix LoadDeploymentState to check Pipeline:ClearCache instead of Publishing:ClearCache

[Copilot]

The LoadDeploymentState method was checking the wrong configuration key, causing the --clear-cache flag to be ignored during deployment state loading.

Changes

• Updated DistributedApplicationBuilder.LoadDeploymentState() to read from Pipeline:ClearCache instead of Publishing:ClearCache

Context

The --clear-cache command-line switch maps to Pipeline:ClearCache in the configuration system. The rest of the codebase (FileDeploymentStateManager, PipelineOptions, tests) already uses Pipeline:ClearCache, but LoadDeploymentState was checking a non-existent Publishing:ClearCache key, causing it to always return false and load cached state even when --clear-cache was specified.

- var clearCache = _innerBuilder.Configuration.GetValue<bool>("Publishing:ClearCache");
+ var clearCache = _innerBuilder.Configuration.GetValue<bool>("Pipeline:ClearCache");

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 build /tmp/aspirebEQr20/teststorage.module.bicep --stdout (dns block)
  • Triggering command: /usr/local/bin/bicep build /tmp/aspireHAKv39/teststorage.module.bicep --stdout (dns block)
  • Triggering command: /usr/local/bin/bicep build /tmp/aspirehKoUIN/env.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)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Fix clear cache handling for deployment state loading</issue_title>
<issue_description>The code below needs to be updated to check for the configuration value in the Pipeline:ClearCache.

aspire/src/Aspire.Hosting/DistributedApplicationBuilder.cs

Line 750 in 5281500

var clearCache = _innerBuilder.Configuration.GetValue<bool>("Publishing:ClearCache");

</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Fix clear cache handling for deployment state loading #12451

---

💡 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 -- 12452

Or

• Run remotely in PowerShell:

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

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

Or

• Run remotely in PowerShell:

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

[Copilot]

Pull Request Overview

This PR fixes a bug where the --clear-cache command-line flag was being ignored during deployment state loading. The LoadDeploymentState method was checking the wrong configuration key (Publishing:ClearCache) instead of the correct key (Pipeline:ClearCache), which is where the --clear-cache flag actually maps to in the configuration system.

Key Changes

• Updated LoadDeploymentState() to check Pipeline:ClearCache configuration key instead of Publishing:ClearCache