Skip to content

v2020.1.0
Compare
Choose a tag to compare
@lukaszbudnik lukaszbudnik released this 10 Mar 20:32
v2020.1.0
13cf713
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Version numbering change

What would have been v5.0 has become v2020.1.0. This change was made primarily to differentiate API version numbering from migrator versioning. Going forward migrator will use a year as a major version number.

API versions

migrator v2020.1.0 supports the following API versions:

  • v1 - REST API
  • v2 - GraphQL

New Features

Latest and greatest features are:

  • DB versioning - every migrator action creates a new DB version. This feature can be used for troubleshooting and tracing DB modifications in dev environments but is also an ideal tool for auditing and compliance. GraphQL API v2: createVersion and createTenant and API v1: POST migrations and POST tenants create a new DB version. However, DB versions are only accessible in API v2. Meaning you can still use API v1 and migrator will create DB versions for you, but you have to use API v2 to access DB versions information;
  • API v2 - GraphQL API - the migrator's API v1 was pretty verbose and was producing sometimes rather big HTTP responses. There were half-measures implemented like response parameter (full - all data, list - list of applied migrations, summary - only summary). With GraphQL you now have a full control over what you want migrator to return. See examples in data package and README.md;
  • API v2 no longer verifies checksums of applied source migrations - the rationale is that once applied source migrations are never re-applied. Further with disabling verification of checksums you can now flatten DB migrations (as a best practice DB migrations/evolutions should be flattened on a regular basis).
Assets 2
Loading