0

We currently use Dbup for SQL deployment. I would like to configure Dbup to allow for the use of a manifest file for deployment. I envision a directory with a manifest file for each release, the manifest file containing the file name (or perhaps path and name) of the file that should be deployed at the next upgrade. So Dbup, rather than running all the scripts it hasn't run yet, would got look at the latest manifest file, and would only run the scripts in the manifest file. Is this possible with existing Dbup functionality? If not, how could I accomplish it?

hyphen
  • 2,368
  • 5
  • 28
  • 59
  • Are you currently using the `WithScriptsEmbeddedInAssembly` approach? – Stewart Ritchie Jun 12 '20 at 16:48
  • @StewartRitchie I'm using WithScriptsFromFileSystem – hyphen Jun 12 '20 at 16:55
  • I could switch to WithScriptsEmbeddedInAssembly if it will help accomplish the goal..Maybe there's some built in way to do this already and I just don't know about it. – hyphen Jun 12 '20 at 16:58
  • 1
    The `WithScripts` method gives the most control. Create a class to read your manifest file and return a collection of `SqlScript` objects with the contents of your source files. – Stewart Ritchie Jun 12 '20 at 19:02

0 Answers0