Update retry in Kusto emulator actions to handle any non-permanent error

[MattKotsenas]

Description

Previously, the resilience pipeline used to create the Kusto databases had two shortcomings:

1. Only handled the throttle exception
2. Relatively long delay before retry

Address both of those issues by:

• Extract the resilience pipeline into its own internal class so it can be tested
• Update the pipeline to handle exceptions that implement Kusto's common interface
• Update the pipeline to use a shorter timeout but with more tries and an exponential backoff

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
    • Link to aspire-docs issue (consider using one of the following templates):
      • New (or update) doc-idea template
      • New breaking-change template
      • New diagnostic template
  • No

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

Or

• Run remotely in PowerShell:

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

[Copilot]

Pull Request Overview

This PR improves the retry logic for Azure Kusto emulator operations by making it more robust and configurable. The changes extract the resilience pipeline into a dedicated class and expand retry capabilities beyond just throttle exceptions.

Key changes:

• Creates a new internal class to handle Kusto-specific resilience patterns with improved retry configuration
• Replaces the inline pipeline with a more comprehensive solution that handles any non-permanent Kusto exception
• Adds comprehensive unit tests to verify retry behavior for different exception types

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
src/Aspire.Hosting.Azure.Kusto/AzureKustoEmulatorResiliencePipelines.cs	New internal class providing pre-configured resilience pipeline with exponential backoff and transient error detection
src/Aspire.Hosting.Azure.Kusto/AzureKustoBuilderExtensions.cs	Removes inline pipeline definition and uses the new centralized resilience pipeline
tests/Aspire.Hosting.Azure.Kusto.Tests/KustoResiliencePipelinesTests.cs	Adds unit tests covering retry behavior for temporary, permanent, and non-Kusto exceptions

[davidfowl]

Do we want to backport this to 9.5.1?

[eerhardt]

/backport to release/9.5

[github-actions]

Started backporting to release/9.5: https://github.com/dotnet/aspire/actions/runs/18166908504

[eerhardt]

Do we want to backport this to 9.5.1?

I don't think it will hurt. Customer feedback we've heard on a new integration.