Aspire CLI: do command, multiple do's?

[Matthew Paul (mip1983)]

I've used the 'aspire do' command so I can deploy individual projects in my build pipeline (a user can click the individual parts they want to deploy and it'll run the 'aspire do deploy-' for each).

I'm wondering if it would be possible/more efficient to be able to pass multiple things to 'do', so it could consolidate into one action (potentially avoid some provisioning repetition)? i.e.

aspire do [deploy-project-a, deploy-project-b]

[Vahid Saadat (vst121)]

aspire do intentionally runs a single action at a time.

Recommended approaches instead:

1. Create a composite action
   Define a single deploy-all (or similar) action that deploys multiple projects in one go.

2. Keep the pipeline orchestration external
   Let the CI pipeline decide which aspire do deploy-* commands to run; that’s the intended usage model.

3. Refactor shared provisioning
   Move common infrastructure into a shared action so repeated runs stay cheap.

So, while batching would look convenient, it cuts against how aspire do is structured today. If this is something you want long-term, it’s worth opening a feature request, but for now, one action per invocation is the supported path.