Poll

Automatic Teams Trial and Upgrading to Flyway Teams

Flyway allows you to use the Teams edition with all of its features within the first 28 days from your first deployment, after which it will revert to Community Edition unless you sign up for a free trial or purchase a full license.

Upgrading from Community

If you are currently using Flyway Community and have obtained a Flyway Teams license, please see license key to read about where to configure this License Key.

Command Line

If you are using the command line, simply provide your license key through any of the supported methods.

For example:

./flyway -licenseKey=FL01... info

API

If you are using the API, simply swap your dependency from org.flywaydb.flyway to org.flywaydb.flyway.enterprise. Then provide your license key through any of the supported methods.

For example:

// gradle
dependencies {
    compile 'org.flywaydb.enterprise:flyway-core:8.4.1'
}

// code
Flyway flyway = Flyway.configure()
    .licenseKey("FL01...")
    .load();
flyway.info();

Gradle

If you are using the Gradle plugin, swap the plugin dependency from id "org.flywaydb.flyway" version "8.4.1" to id "org.flywaydb.flyway.enterprise" version "8.4.1". Then provide your license key(/documentation/configuration/parameters/licenseKey) through any of the supported methods.

For example:

plugins {
    id "org.flywaydb.flyway.enterprise" version "8.4.1"
}

flyway {
    licenseKey = 'FL01...'
}

Maven

If you are using the Maven plugin, swap the plugin dependency from <groupId>org.flywaydb</groupId> to <groupId>org.flywaydb.enterprise</groupId>. Then provide your license key through any of the supported methods.

For example:

<plugin>
    <groupId>org.flywaydb.enterprise</groupId>
    <artifactId>flyway-maven-plugin</artifactId>
    <version>7.0.0</version>

    <configuration>
        <licenseKey>FL01...</licenseKey>
    </configuration>
</plugin>

New Features

Now that you are using the Teams edition of Flyway, you can take advantage of all the powerful new features at your disposal:

• Begin creating Undo migrations to allow rollback of deployments.
• Begin storing your migrations in cloud storage such as Amazon S3 or Google Cloud Storage.
• Begin writing migrations in languages other than SQL and Java using script migrations.
• Preview your deployments, or execute them outside of Flyway using Dry Runs.
• Optimise the execution of migrations using batching or streaming.
• Gain more control over your deployments by cherry picking which migrations to execute.
• Apply migrations manually outside of Flyway but update the schema history using mark as applied.
• Guaranteed support for databases up to 10 years old.
• Leverage the power of Oracle SQL*Plus in your migrations.
• Promote database warnings to errors, or ignore errors thrown during execution with error overrides.

… and much more. See parameters for all the Teams configuration parameters.