Repository Docs & Knowledge Base

Consolidated Spensara documentation repository (722 Markdown & architecture documents in ../repository)

Automation workflows, orchestration references, and developer tooling guides.

agent-tooling/.agents/skills/aspire-orchestration/references/resource-management.md 1,934 bytes · Updated Oct 23, 2026 10:44 AM EDT

Raw File

Resource Management

Use this when the task is scoped to one resource or depends on a specific resource becoming healthy.

bash

aspire wait <resource>
aspire wait <resource> --status up --timeout 60

Use aspire wait before a dependent action when readiness is the blocker.
Add --status and --timeout for explicit readiness conditions.
Treat readiness as resource-scoped — a missing ready signal is not a reason to restart the whole AppHost.
Use displayName from aspire ps --format Json, not name (#15842).

bash

aspire resource <resource> start
aspire resource <resource> stop
aspire resource <resource> <command>

Prefer resource-scoped commands when the task doesn't require an AppHost-wide restart.
If one resource is wedged, use resource-scoped commands such as stop, start, or rebuild when the resource exposes them before escalating to a full AppHost restart.
Use aspire resource <resource> <command> when the AppHost exposes resource-specific dashboard or operational commands.
If the resource's own framework watch/HMR/debug workflow is already handling the change, do not force an Aspire resource command.

What Changed	Action	Command
AppHost project (Program.cs, .csproj)	Full restart	`aspire stop` → edit → `aspire start`
.NET service project (.cs files)	Rebuild/refresh resource if exposed	`aspire resource <name> rebuild` or the resource's IDE/watch workflow
JavaScript/Python/Go files	Usually no Aspire action	File watchers/HMR handle it automatically
Configuration (appsettings.json)	Check first	`aspire describe` then decide
TypeScript AppHost deps	Restore	`aspire restore`