You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
aspire deploy should support reusing assets from previous aspire publish runs #10620
Currently, running aspire publish followed by aspire deploy on the same output path doesn't reuse the previously published assets. There's no clear workflow for deploying assets that have already been published without rebuilding them.
The current behavior will always regenerate which feels too aggressive. I think we should get towards a place where deploy can re-use.
Or does it only use them if they exist or are out of date?
I think to start we can have an explicit opt-in aspire deploy --no-publish or something that will reuse assets in the generated output path instead of rebuilding. We could also do a more interactive UX where we detect if there are existing assets and prompt the user if they would like to reuse them. The --no-publish flag could be the flag to set that value.
We could evolve that UX to be able to detect if they are out-of-date and skip prompting for reuse if they are and always need to be regenerated.
Activity
davidfowl commentedon Jul 23, 2025
Reuse or re-generate? Or does it only use them if they exist or are out of date?
captainsafia commentedon Jul 23, 2025
The current behavior will always regenerate which feels too aggressive. I think we should get towards a place where deploy can re-use.
I think to start we can have an explicit opt-in
aspire deploy --no-publishor something that will reuse assets in the generated output path instead of rebuilding. We could also do a more interactive UX where we detect if there are existing assets and prompt the user if they would like to reuse them. The--no-publishflag could be the flag to set that value.We could evolve that UX to be able to detect if they are out-of-date and skip prompting for reuse if they are and always need to be regenerated.
davidfowl commentedon Oct 21, 2025
Not doing this any,pre