Migrations Bundles: Provide more info about the bundle

Today the bundle is effectively just dotnet ef database update, but I’ve been thinking it would be helpful to include gestures for these commands too in the bundle:

• dotnet ef dbcontext info (or even just a way to see the DbContext type of the bundle in --help)
• dotnet ef migrations list
• dotnet ef migrations script (although this seems much less important since you can just generate a script instead of a bundle in the first place)

[bricelam]

We solved the issues I listed there in EF Core 5.0 which made the script a lot more robust.

The problems that still exist with the script which are solved by bundles are:

• They need something (usually database-specific) to execute them (Sqlcmd, SSMS, MSDeploy, etc.)
• Most tools that execute SQL Server scripts simply continue on to the next statment when they encounter an error. This can leave the database in a very bad state
• Transaction handling isn’t always obvious. For example, MSDeploy appears to completely ignore the BEGIN and END statements and tries to wrap everything into a single transaction

If you have a working solution, there’s no need to move to bundles. Bundles simply enable more databases to achieve the same rich experience on more platforms.

[wdhenrik]

Please consider this an emphatic vote for validating how a bundle will change a target. I’m looking for something like: bundle --connection [connection string] --script-pending --output [output path]

I’m using bundles in CI/CD and there doesn’t seem any way for me to verify what changes will take place when run against a specific target. I’m generating a single bundle artifact in CI and want to use that all the way through the CD stack.