Handle non-interactive interaction service availability for resource commands

[James Newton-King (JamesNK)]

Summary

• track non-interactive resource command execution in InteractionService using an AsyncLocal scope
• make IInteractionService.IsAvailable return false during non-interactive CLI resource command execution
• update EnsureServiceAvailable error text to clarify it can be unavailable in non-interactive CLI command contexts
• add/adjust tests across hosting, CLI unit, and CLI E2E coverage

Changes

• ResourceCommandService now scopes command execution with InteractionService.StartNonInteractiveScope() when NonInteractive is true
• InteractionService now:
  • tracks non-interactive scope with AsyncLocal<bool>
  • checks scope in IsAvailable
  • has updated EnsureServiceAvailable exception message
• Added/updated tests:
  • hosting tests for IsAvailable non-interactive scope behavior
  • hosting tests for non-interactive vs interactive command execution behavior
  • CLI unit test for resource command failure path with interaction service unavailable
  • new CLI end-to-end ResourceCommandTests that executes aspire resource against a command that prompts and fails due to EnsureServiceAvailable

Validation

• dotnet test --project tests/Aspire.Cli.Tests/Aspire.Cli.Tests.csproj -- --filter-method "*.ResourceCommand_FailsWhenCommandUsesInteractionService" --filter-not-trait "quarantined=true" --filter-not-trait "outerloop=true"
• dotnet build tests/Aspire.Cli.EndToEnd.Tests/Aspire.Cli.EndToEnd.Tests.csproj /p:TreatWarningsAsErrors=false

Fixes #16720

[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/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 16973

Or

• Run remotely in PowerShell:

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

[Copilot]

Pull request overview

This PR updates Aspire Hosting’s InteractionService and resource command execution so that resource commands executed in non-interactive CLI contexts can detect that prompting isn’t allowed (via IInteractionService.IsAvailable == false), and adds coverage across hosting, CLI unit, and CLI E2E tests.

Changes:

• Add an AsyncLocal-backed non-interactive scope in InteractionService that forces IsAvailable to false while active.
• Scope resource command execution (ResourceCommandService) so command callbacks run under the non-interactive scope when NonInteractive=true.
• Add/adjust hosting + CLI unit + CLI E2E tests for the non-interactive behavior and failure path.

Reviewed changes

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

Show a summary per file

File	Description
src/Aspire.Hosting/ApplicationModel/ResourceCommandService.cs	Wraps command execution in a non-interactive scope when NonInteractive=true.
src/Aspire.Hosting/InteractionService.cs	Introduces AsyncLocal non-interactive scoping and updates the unavailable-service error message.
tests/Aspire.Hosting.Tests/InteractionServiceTests.cs	Adds tests for non-interactive scoping and AsyncLocal flow/nesting.
tests/Aspire.Hosting.Tests/ResourceCommandServiceTests.cs	Validates IsAvailable behavior during interactive vs non-interactive command execution.
tests/Aspire.Cli.Tests/Commands/ResourceCommandTests.cs	Adds CLI unit coverage for failure path when interaction service is unavailable.
tests/Aspire.Cli.EndToEnd.Tests/ResourceCommandTests.cs	Adds an E2E scenario verifying a resource command that requires prompting fails appropriately.

[github-actions]

Re-running the failed jobs in the CI workflow for this pull request because 1 job was identified as retry-safe transient failures in the CI run attempt.
GitHub was asked to rerun all failed jobs for that attempt, and the rerun is being tracked in the rerun attempt.
The job links below point to the failed attempt jobs that matched the retry-safe transient failure rules.

• Tests / Hosting-1 / Hosting-1 (windows-latest) - Job-level runner or infrastructure failure matched the transient allowlist.

[David Fowler (davidfowl)]

Makes me feel sick but it works

[github-actions]

Re-running the failed jobs in the CI workflow for this pull request because 1 job was identified as retry-safe transient failures in the CI run attempt.
GitHub was asked to rerun all failed jobs for that attempt, and the rerun is being tracked in the rerun attempt.
The job links below point to the failed attempt jobs that matched the retry-safe transient failure rules.

• Tests / Cli.EndToEnd-KubernetesDeployWithSqlServerTests / Cli.EndToEnd-KubernetesDeployWithSqlServerTests (ubuntu-latest) - Test execution failure will be retried because 1 failed test(s) matched transient test failure patterns (Unable to access container registry during publish).

Matched test failure patterns (1 test)

• Aspire.Cli.EndToEnd.Tests.KubernetesDeployWithSqlServerTests.DeployK8sWithSqlServer — Unable to access container registry during publish