outrigger - npm Package Versions

0.5.0

Released 2016-02-10

Major Changes

• Deprecated the project. The functionality has been migrated to juttle-engine.

0.4.0

Released 2016-01-22

Major Changes

• NOTICE: As part of the update to juttle 0.3.0, the configuration syntax for adapters changed from the name of the module (e.g. "juttle-elastic-adapter") to the type of the adapter ("elastic").
• Errors from juttle programs are now shown in the outrigger browser window [#29].
• Add a "Show Juttle" link that shows the source code of the current program [#59].
• Include OpenTSDB support [#116].

Minor Changes

• Rearrange all example programs so they can be run from a single set of docker-compose files. [#80]
• Embed all example juttle programs in the base outrigger docker image so they can be run without having to git clone the outrigger repository first. [#104]
• Minor changes to Travis-CI configuration to reflect the changes in [#48].
• Add unit tests for browser/outriggerd interactions. [#12]
• Expose the juttle CLI in the bin directory of the outrigger installation. [#86]
• Add example programs for the gmail adapter. [#89]
• Switch to using eslint for lint checking, which also includes changes to style enforcement. [#90].
• Add example programs for influx integration using monitoring of docker containers with cAdvisor. [#23]
• Add additional other example programs. [#110]

Bug Fixes

• Prevent a race condition where a short-lived program could start, run, and stop before the browser could open a websocket to receive the program's output. [#64]
• Fix innocuous ERROR in outrigger logs related to sending commands to an already-closed subprocess. [#82]

0.3.0

Released 2016-01-13

Major Changes

• Add support for running example programs using docker. An outrigger container is now available on docker hub.
• Add support for editor-driven/remote outrigger program management. Instead of specifying files directly via run?path=<path>, the browser can load a page run?rendezvous=<session>. outrigger-client's push and watch commands push programs to the browser for a given session. This allows for running a client/editor on a different host than the host running outrigger. [#13]
• The browser app served by outrigger now uses a standalone javascript library which implements the client half of the JSDP and Jobs APIs supported by outrigger.
• Outrigger now explicitly depends on a specific version of juttle and specific versions of all juttle adapters. Subsequent releases will move the dependent versions forward as necessary. [#48]

Minor Changes

• New command line options -l/--log-level, -L/--log-config, and -o/--output allow specifying an alternate location for log4js config, or simply changing the log level and/or location. [#45]
• New command line options -c/--config allows specifing an explicit path to a juttle config file [#46]
• New command line option -d/--daemonize enables explicit backgrounding.
• Add additional demo programs that show various capabilities of juttle.
• Add code coverage tests. [#42]

Bug Fixes

• Make sure a custom path for --config was being passed all the way to the subprocess that runs a juttle program [#62]