Flyway Editions

• The Flyway Community edition contains all the core (free) features as well as Teams or Enterprise features which are made available based on your license.

• The Flyway Open Source edition just contains the open source components so upgrading requires a different installation of Flyway.

  Upgrading to Flyway Teams or Enterprise

This article assumes you are a proud owner of a Flyway Teams / Enterprise license.

If you are not, head over to Redgate Products Trial to start a free trial. Alternatively, you can start a free trial using the auth command.

Command Line

Upgrading from Community

If you are currently using Flyway Community Edition then all you need do is authenticate with your Redgate credentials (see Auth) or provide a License Key to unlock the advanced capabilities Flyway offers.

Upgrading from Open Source

If you have been using the Open Source version of Flyway then you will need to download the Flyway Community Edition first.

API

See details for Flyway Community in Java(API)

For example:

// gradle
dependencies {
    implementation 'com.redgate.flyway:flyway-core:10.11.1'
}

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

Gradle

See details for Flyway Community in Gradle Task.

For example:

plugins {
    id "com.redgate.flyway.flyway" version "10.11.1"
}

flyway {
    licenseKey = 'FL01...'
}

Maven

See details for Flyway Community in Maven Goal.

For example:

<plugin>
    <groupId>com.redgate.flyway</groupId>
    <artifactId>flyway-maven-plugin</artifactId>
    <version>10.11.1</version>

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

New Features

Now that you are using the Teams / Enterprise 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.
• 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.