[Beta Must Have] Migrations: KRE Command Line Interface

[rowanmiller]

• k ef context list
• k ef context use [context]
• k ef migration add [name] -context <context>
• k ef migration list -context <context>
• k ef migration apply [migration] -context <context>
• k ef migration script [from] [to] -idempotent -context <context>

[bricelam]

Here are some notes from the design meeting on August 21.

• Needs to be a premiere experience like PowerShell
  • Use convention over configuration
    • Infer things about the project
      • Migrations directory
  • Correlate command names with PowerShell commands
  • Short, terse parameter names
    • Possibly one-letter aliases
  • Logging
    • Similar to current tools
    • Show SQL, etc with --verbose
    • Report errors
    • Report success
  • Help (git-like)
  • Needs ASCII art (like azure.exe)
  • Syntax highlighting?
• Will the user be required to install this package and add a command to their project.json?
  • May be able to do this using "design-time dependencies". Need to understand these more.
  • Is "k migrations" the right name?
    • Probably "k migrate" or "k ef" instead
• Should we also have a standalone .exe?
  • Yes
  • Good for MSBuild
  • NuGet.exe uses ILMerge to make .exe self-contained, we should consider doing this too.
• Does it need to scaffold?
  • Yes, for non-VS users (e.g. on OSX)
• Can we use .json instead of .ini?
• Is the config stuff necessary?
  • Consuming, possibly.
  • Creating, probably not.

[felipepessoto]

Please, update the design meeting notes

[bricelam]

@fujiy We talked more about this in today's design meeting. @ajcvickers should post notes in a day or so. It will (most likely) contain details on the decisions we made in the August 21 meeting.