sbt-conductr is an sbt plugin provides commands that communicate with ConductR from within an sbt session. It can also be used in conjunction with sbt-bundle to deploy your application or service to ConductR without leaving the comforts of sbt.

sbt-conductr is enabled by simply declaring its dependency:

resolvers += "Typesafe repository" at "http://repo.typesafe.com/typesafe/releases/"
addSbtPlugin("com.typesafe.conductr" % "sbt-conductr" % "1.2.1")

The plugin has no requirements for other plugins to be enabled.

The IP address of the ConductR host is automatically retrieved and used if:

• ConductR is running on the same host inside a docker container. The ConductR address is set to http://{docker-host-ip}:9005.
• ConductR is running on the same host. The ConductR address is set to http://{hostname}:9005.

In other scenarios it is necessary yo set the address to the ConductR control server manually, e.g. if ConductR is running on 192.168.59.103:9005 you will issue the following command from the sbt console:

controlServer 192.168.59.103:9005

This then sets the sbt session up to subsequently communicate with the ConductR at 192.168.59.103 on port 9005. You may type commands such as:

conduct info

...which will obtain information on the ConductR cluster.

If you have sbt-bundle enabled e.g.:

lazy val root = (project in file(".")).enablePlugins(JavaAppPackaging)

You can then produce a bundle by typing:

bundle:dist

...and then load the bundle by typing:

conduct load <HIT THE TAB KEY AND THEN RETURN>

Using the tab completion feature of sbt will produce a URI representing the location of the last distribution produced by the native packager.

Hitting return will cause the bundle to be uploaded. On successfully uploading the bundle the plugin will report the BundleId to use for subsequent commands on that bundle.

When loading a bundle you can also load configuration if there is any e.g.:

configuration:dist

...and then hit the tab key after specifying the bundle for conduct load.

The log messages and events of a particular bundle can be displayed with the commands:

conduct logs my-bundle
conduct events my-bundle

Make sure that your logging infrastructure is up an running. Otherwise the command will timeout:

[trace] Stack trace suppressed: run last conductr-service-lookup/*:conduct for the full output.
[error] (conductr-service-lookup/*:conduct) java.util.concurrent.TimeoutException: Futures timed out after [5 seconds]
[error] Total time: 5 s, completed Sep 28, 2015 11:40:47 AM

With sbt-conductr-sandbox you can start the default logging infrastructure during ConductR cluster startup easily:

sandbox run --withFeatures logging
conduct logs my-bundle

Give the logging infrastructure enough time to start before entering the logs or events command.

The following sbt-conductr commands are available:

In addition the following settings are available:

© Typesafe Inc., 2014-2015