Replies: 1 comment
-
|
aspire do intentionally runs a single action at a time. Recommended approaches instead:
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. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
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]Beta Was this translation helpful? Give feedback.
All reactions