Scenario: Improve the local database development experience

[davidfowl]

We have several issues that need to be resolved for this end to end to come together nicely (and to reduce the friction)

• - Postgres/SQL Server EF components make it hard to run dotnet ef to create migrations, etc. #398
• - Make it easier to use external volumes for database containers #837
  • - Split WithVolumeMount into two seperate methods #1437
• - The argument for AddDatabase represents a database and a connection string name at the same time #1199
• - Option to set up and keep resources (containers) after AppHost shutdown  #923
• - Should EF-based components reference Microsoft.EntityFrameworkCore.Design? #740
• - Automatically persist generated password for all containers with user names and passwords #1151
• - Add support for adminer for mysql #1936
• - Add support for mongo express #1920
• - Connection to SQL Server (was Azure SQL Edge) Fails When .NET API Is Started Using an Aspire Host (Issue Limited to macOS?) #1023 - Slowness booting up SQL on MacOS
• Add a hosting helper method for adding a persistent volume mount to containers #1132

This sample shows the state of the art today:

• https://github.com/dotnet/aspire-samples/tree/main/samples/DatabaseContainers

Big issues that have been themes:

• Calling AddDatabase on our database server types, should create the database at dev time (with an opt out).
• We have to come up with guidance on how people run EF migrations when using aspire
• We should make it easy to use a persistent volume (and persistent container?) when working with a database locally
• We should make it easier to use database tools with databases orchestrated by aspire (today we generate random passwords)

[davidfowl]

Moved to P4

[kkirkfield]

Good day @davidfowl and @JamesNK. I started a proof of concept for some new API changes at #2090. Would greatly appreciate your thoughts. Thank you!

[davidfowl]

Moving this to the backlog,

[davidfowl]

Closing this tracking issue