§Lagom 1.5 Migration Guide
This guide explains how to migrate from Lagom 1.4 to Lagom 1.5. If you are upgrading from an earlier version, be sure to review previous migration guides.
Lagom 1.5 also updates to the latest major versions of Play (2.7), Aka (2.5.18) and Akka HTTP (10.1). We have highlighted the changes that are relevant to most Lagom users, but you may need to change code in your services that uses Play APIs directly. You’ll also need to update any Play services in your Lagom project repositories to be compatible with Play 2.7. Please refer to the Play 2.7 migration guide (https://www.playframework.com/documentation/2.7.0-RC8/Migration27), Akka 2.5.18 release announcement and the Akka HTTP 10.1.0 release announcement for more details.
The version of Lagom can be updated by editing the
project/plugins.sbt file, and updating the version of the Lagom sbt plugin. For example:
addSbtPlugin("com.lightbend.lagom" % "lagom-sbt-plugin" % "1.5.0-RC1")
We also recommend upgrading to sbt 1.2.1 or later, by updating the
Lagom 1.5.0 now has support for SSL calls for gRPC integration and a new build setting was introduced to configure the https port for a given service manually.
In sbt, the new setting is called
lagomServiceHttpsPort. To keep the names aligned, we are deprecating
lagomServicePort in favour of
TODO: add links to gRPC integration and SSL support documentation.
were never intended for public consumption, and therefore have been marked deprecated in 1.5.0 for removal in
ConductR is no longer supported with Lagom 1.5.
We recommend migrating to Kubernetes, DC/OS or another deployment solution before upgrading.
Lighbend Orchestration is an open-source suite of tools that helps you deploy Lagom services to Kubernetes and DC/OS. It provides an easy way to create Docker images for your applications and introduces an automated process for generating Kubernetes and DC/OS resource and configuration files for you from those images. This process helps reduce the friction between development and operations. If you are using Kubernetes or DC/OS, or interested in trying one of these platforms, we encourage you to read the Lightbend Orchestration documentation to understand how to use it with Lagom and other components of the Lightbend Reactive Platform.
If you are not using Kubernetes or DC/OS, you must configure your services in a way that suits your production environment. See Running Lagom in production for more information.
If you are using ConductR in production and need assistance migrating to other solutions please contact Lightbend.
TODO (new version required)
A new mechanism to form and join an Akka Cluster is introduced in Lagom 1.5. Apart from the original
Manual Cluster Formation the new
Akka Cluster Bootstrap is now supported. This new mechanism is introduced with lower precedence than
Manual Cluster Formation so if you rely on the use of a list of
seed-nodes then everything will work as before. On the other hand,
Akka Cluster Bootstrap takes precedence over the
join-self cluster formation for single-node clusters. If you use single-node clusters via
join-self you will have to explicitly disable
Akka Cluster Bootstrap:
lagom.cluster.bootstrap.enabled = false
§Upgrading a production system