"bin/kong migrate" should be embedded into "bin/kong start" about kong

[thibaultcha]

• Agree for running the migration the first time.
• Agree for the message saying the migration is not up to date
• Disagree for the [y/n] quick migration process. A migration is something that should not happen too often. It is something a user should really think through: backup the data, shutdown or maintenance-mode his kong cluster, run, check if good, bring back up. Emphasis on backup the data because I think it's the most important one and will be required even for single-node, non-cassandra clusters in the future.

[subnetmarco]

Regarding you third point, I agree. In the future, we could treat potential breaking migrations differently. For example a potential breaking migration is something that updates an existing table and the user should be careful doing it. But on the other side a migration that just adds new tables to the keyspace won't do any harm to the existing data, so we should still notify the user but we can let him execute the migration after showing a [y/n] prompt.

[thibaultcha]

Maybe later, but I think it's out of scope at this point. And I still don't think we should quick run migrations anyways. Big or small ones.

Let's make quick easy first migration, and an error if not migrated to the latest available. And pretty print any error. That's in the scope of the current state of Kong, being in beta etc. Will close this issue once done.

[subnetmarco]

Ok I agree. Let's implement the first two points.