Description
Type of issue
Missing information
Description
The documentation to publish an Aspire project is awesome. But in my opinion, it lacks a paragraph on the best solution to deploy an update. Should I run again azd up ? Should I update the api service only if I didn't touch the frontend project ? Will it works ? (i could test and see what happens but if every developper has to play to find out the answer, maybe it could be useful to update the documentation to add some details on the workflow to use to update an Aspire solution.
I don't know what's the best solution to update an existing deployed Aspire project.
Right now, it seems to deploy Redis each time I deploy. It also adds a new line in my Aspire dashboard each time I deploy an update.
Is it because I keep using azd up instead of updating container by container once it has been deployed once ?
See the picture below :
You can see that I have an app line for each update. Is it possible to clean the logs from time to time ?
Maybe it's not an issue and it's just a way to see the logs by release / update ?
Page URL
Content source URL
Document Version Independent Id
c4fd539b-5f60-2dd0-0bf1-d0a218b99427
Platform Id
55bdce84-153e-da0f-f4e8-07fc2f41d143