Skip to content

Remove resource data from aspire ps — use describe for resource streaming #17472

@JamesNK

Description

@JamesNK

From unaddressed review comment in #16836: #16836 (comment)

Problem

aspire ps now includes resource data (via --resources flag), but ps is intended for AppHost-level information. We already have describe that streams resource changes.

Including resources in ps means that every time a single resource changes, ps would return every resource on the AppHost — this is redundant with describe and produces unnecessarily large output.

Proposed Fix

Remove resource data from ps output. Consumers that need resource information should use describe instead.

This follows the same pattern established by Kubernetes and Docker CLIs, where there is a clear separation between summary/list commands and detailed inspection commands:

  • Kubernetes: kubectl get pods (summary list) vs kubectl describe pod <name> (detailed resource information)
  • Docker: docker ps (list running containers) vs docker inspect <container> (detailed container information)

Similarly, aspire ps should remain a lightweight summary of running AppHosts, while aspire describe provides detailed resource-level information and streaming.

/cc @mitchdenny

Metadata

Metadata

Assignees

Labels

area-app-modelIssues pertaining to the APIs in Aspire.Hosting, e.g. DistributedApplication

Type

No type
No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions