Releases: lightbend/sbt-reactive-app
1.7.3
1.7.2
1.7.1
1.7.0
Secure Docker image building with sbt-native-packager 1.3.17
For building Docker images, Lightbend Orchestration depends on sbt-native-packager, an sbt plugin maintained by Nepomuk "Muki" Seiler. To improve the security around file permissions and Red Hat OpenShift compatibility, Lightbend Tooling team has contributed a few enhancements to sbt-native-packager.
First, dockerPermissionStrategy was added to decide how file permissions are set for the working directory inside the Docker image. The default DockerPermissionStrategy.MultiStage strategy uses multi-stage Docker build to call chmod ahead of time. This avoids extra Docker layer overhead.
Next, dockerChmodType setting was added to specify what file permissions are set for the working directory. By default, it uses DockerChmodType.UserGroupReadExecute, which prevents the working directory to be writable. If you want your application to write a file, the following setting can be used to opt-in:
import com.typesafe.sbt.packager.docker.DockerChmodType
dockerChmodType := DockerChmodType.UserGroupWriteExecuteSee sbt-native-packager 1.3.16 release note for more details.
How to upgrade to Lightbend Orchestration 1.7.0
Note that there are breaking changes in Lightbend Orchestration 1.7.0. First upgrade sbt-reactive-app in all of your projects, and then upgrade reactive-cli (rp). This is because reactive-cli requires the minimum version of sbt-reactive-app to be 1.7.0.
sbt-reactive-app can be upgraded by bumping the version in your project/plugins.sbt:
addSbtPlugin("com.lightbend.rp" % "sbt-reactive-app" % "1.7.0")On macOS for example, reactive-cli can be upgraded as follows:
brew upgrade lightbend/tools/reactive-cli
YAML file generation for Akka Cluster Bootstrapping using Kubernetes API
The main feature of Lightbend Orchestration is the automatic generation of Kubernetes configuration (YAML) files.
For Akka Cluster Bootstrapping, Lightbend Orchestration generates YAML files using Kubernetes API as the discovery method. Starting with Lightbend Orchestration 1.7.0, we will use a specialized label akka.lightbend.com/service-name, which denotes the Akka Cluster to join when a pod comes up.
- The value of the this label will default to either the app name or the app name + version depending on the deployment type.
- Deployment pods are labeled with
"akka.lightbend.com/service-name": "friendimpl"etc. - You can override the label selector as follows:
-Dakka.discovery.kubernetes-api.pod-label-selector=akka.lightbend.com/service-name=%s(as opposed to usingapp=%s). - You can override the effective name as follows:
-Dakka.management.cluster.bootstrap.contact-point-discovery.effective-name=friendimpletc.
YAML file generation: Removal of automatic port assignment
Previous releases of Lightbend Orchestration automatically assigned various port numbers from port 10000 in part by overriding your application.config file. Lightbend Orchestration 1.7.0 removes this feature, and respects the port number declared in your your application.config. Otherwise, default port numbers will be used such as port 9000 for Play. This also allows us to remove RP_ENDPOINT_* environment variables, generally simplifying the generated YAML file.
Note: This also means that your deployed service will expose different port number (for example 9000) instead of 10000.
YAML file generation for Akka Cluster Bootstrapping using DNS
Optionally, Lightbend Orchestration 1.7.0 adds experimental support to generate Kubernetes configuration for Akka Cluster Bootstrapping using DNS as the discovery method.
If you want to use DNS, pass --discovery-method=akka-dns to the rp command line. cli#195
Rename of sbt-reactive-app key names
All key names are renamed to prefix with rp and camel cased to comply with Plugins Best Practices. For instance, endpoints setting will now be rpEndpoints, and deploy task will be rpDeploy. The old key names are deprecated and will be removed in the future. sbt-reactive-app#145
Deprecation of SecretReader
In the effort to reduce runtime dependencies, SecretReader was deprecated. Read from the file /rp/secrets/%name%/%key% where %name% is transformed to lowercase, and - for non-alphanum instead. lib#118
Other bug fix
- Fixes missing
protocolwhen UDP endpoint is selected. cli#196
1.6.1
1.6.0
Lightbend Orchestration is a suite of tools that helps you deploy Lagom applications to OpenShift and Kubernetes.
Lightbend Orchestration 1.6.0 is a maintenance release to catch up with Akka Management updates. The development status of Lightbend Orchestration in general is Incubating, and breaking changes are expected in the future.
The reactive-lib 1.6.0 runtime is based on Akka 2.5.18 and Akka Management 0.20.0.
How to upgrade
Make sure to upgrade both reactive-cli and sbt-reactive-app.
On macOS for example, reactive-cli can be upgraded as follows:
brew upgrade lightbend/tools/reactive-cli
sbt-reactive-app can be upgraded by bumping the version in your project/plugins.sbt:
addSbtPlugin("com.lightbend.rp" % "sbt-reactive-app" % "1.6.0")
Akka Cluster bootstrap: port-name
To maintain the compatibility with Akka Management 0.20.0, reactive-lib 0.9.3+ sets the default value of akka.management.cluster.bootstrap.contact-point-discovery.port-name in the config to "akka-mgmt-http". lib#90
In addition, reactive-cli 1.6.0 will generate YAML that passes -Dakka.management.cluster.bootstrap.contact-point-discovery.port-name explicitly from the command line, which allows us to incrementally transition to the port name "management" in the future. cli#185
Akka Cluster bootstrap: discovery-method
Instead of using -Dakka.discovery.method, reactive-cli 1.6.0 will generate YAML that passes -Dakka.management.cluster.bootstrap.contact-point-discovery.discovery-method, which is a setting more specific to Akka Cluster bootstrap. cli#184
Since reactive-lib's ClusterServiceDiscovery was never used, the implementation and akka.discovery.method = reactive-lib in config were both removed. lib#99
Other fixes
- Since Akka 2.5.14+ comes with async-dns, reactive-lib's async-dns implementation was removed. Integration was added to test Akka Cluster bootstrap using DNS on OpenShift. lib#91 by @eed3si9n
- Fixes handling of non-defined
rpDockerPublish. sbt-reactive-app#153 by @dwijnand - Updates the reference to Lightbend helm-charts repo. sbt-reactive-app#159 by @marcoderama
- To fix "No configuration setting found for key 'decode-max-size'", reactive-lib 1.6.0 depends on Akka HTTP 10.0.15. lib#105 by @eed3si9n
- Fixes a typo in Helm RBAC setup. sbt-reactive-app#162 by @yoks
- Fixes inclusion of
application.conffrom transitive dependencies. sbt-reactive-app#165 by @cunei and @eed3si9n