## Migrations

Because we are using SQLAlchemy directly and we don't require any kind of plug-in for it to work with **FastAPI**, we could integrate database <abbr title="Automatically updating the database to have any new column we define in our models.">migrations</abbr> with <a href="https://alembic.sqlalchemy.org" class="external-link" target="_blank">Alembic</a> directly.

)

func init() {
	// Enable klog which is used in dependencies
	klog.InitFlags(nil)
	flag.Set("logtostderr", "true")
	flag.Set("v", "9")
}

func TestMigrate(t *testing.T) {
	migrations := []struct {
		title            string
		memberCount      int
		startVersion     string
		endVersion       string
		protocol         string
		clientListenUrls string
	}{
		// upgrades

And it will work and will be useful **during development**.

But if your connection to the server is lost, the **running process** will probably die.

And if the server is restarted (for example after updates, or migrations from the cloud provider) you probably **won't notice it**. And because of that, you won't even know that you have to restart the process manually. So, your API will just stay dead. 😱

### Run Automatically on Startup

	FileRootSystemCACert = "file-root:system"
)

// TODO: For 1.8, make sure MeshConfig is updated with those settings,
// they should be dynamic to allow migrations without restart.
// Both are critical.
var (
	// Require3PToken disables the use of K8S 1P tokens. Note that 1P tokens can be used to request

Two approaches to migrations stand out:

 * Migrating the existing syntax of your build to Kotlin, bit by bit, while retaining the structure — what we call a _mechanical migration_
 * Restructuring your build logic towards Gradle best practices and switching to Kotlin DSL as part of that effort

Both approaches are viable.
A mechanical migration will be enough for simple builds.

+
The main downside is the extra work required to perform the migration, particularly if the existing build is complex and has many inter-project dependencies.
However, these builds often benefit the most from a switch to idiomatic Gradle.
In addition, Gradle provides many features that can ease the migration, such as the ability to <<ant#sec:using_ant_tasks,use core and custom Ant tasks>> directly from a Gradle build.

This may make migrating between the two seem intimidating, but migrations can be surprisingly easy because Gradle follows many of the same conventions as Maven -- such as the <<java_plugin#sec:java_project_layout,standard project structure>> -- and its dependency management works in a similar way.

Here we lay out a series of steps for you to follow that will help facilitate the migration of any Maven build to Gradle:

If in your use case there's no problem in running those previous steps **multiple times in parallel** (for example if you are not running database migrations, but just checking if the database is ready yet), then you could also just put them in each container right before starting the main process.

### Single Container

ant-task-migration.png...

ant-task-migration.graffle ApplicationVersionco.omnigroup.OmniGraffle7.MacAppStore192.15ColorProfilesdataA/gAAAAUbWVhcwAABAwAAA+wEBAQcBDQETARkBHwElA+gIDAgwCFAIdAiYCLwI4A+wD+QQGBBMEIAQtBDsESARVB+BIwEmgSoBLYExATTBOEE+BQ0FHAUrBToFSQVYBWcF/B9IH5Qf4CAsIHwgyCEYI+EL+QwSDCoMQwxcDHUMjgynD/DpsOtg7SDu4PCQ8lD0EP/PD+wQCRAmEEMQYRB+EJsQuRDXEPURExExEU8R+UUBhQnFEkUahSLFK0Uzh/cYGxhAGGUYihivGNUY+hkgGUUZaxmRGbcZ3RoEG+HukfEx8+H2kflB+/H+ogFSBBIGwgmCDEIPAhHC/HL/4wNTBsMKQw2zESMUoxgj/E0KzRlNJ402DUTNU01hz+ID5gPqA+4D8h...