knot.x 1.3 deployment - Githubissues

knot.x 1.3 significantly changes deployments, as the entire service and its dependencies are shipped as a single ZIP file with the following structure inside:

.
├── bin
│   └── knotx
├── conf
│   ├── application.conf
│   ├── bootstrap.json
│   ├── default-cluster.xml
│   ├── includes
│   │   ├── actionKnot.conf
│   │   ├── hbsKnot.conf
│   │   ├── httpRepo.conf
│   │   ├── server.conf
│   │   ├── serviceAdapter.conf
│   │   └── serviceKnot.conf
│   └── logback.xml
├── knotx-stack.json
├── lib
│   ├── annotations-13.0.jar
│   ├── antlr4-runtime-4.5.1-1.jar
│   ├── commons-collections-3.2.2.jar
│   ├── commons-io-2.5.jar
│   ├── commons-lang3-3.5.jar
│   ├── ...
│   ├── vertx-hazelcast-3.5.0.jar
│   ├── vertx-rx-java2-3.5.0.jar
│   ├── vertx-service-factory-3.5.0.jar
│   ├── vertx-service-proxy-3.5.0.jar
│   ├── vertx-web-3.5.0.jar
│   ├── vertx-web-client-3.5.0.jar
│   └── vertx-web-common-3.5.0.jar
└── logs

Some files/directories from the archive are redundant (bin, logs and knotx-stack.json to be precise) from Chef deployment perspective, so only relevant parts are extracted.

Noteworthy facts:

the entire Git-based part was removed, as it is no longer needed
unzip is a prerequisite now
custom resource properties were refined to adjust them to knot.x 1.3 use case
knotx_instance provider was updated/simplified in a few places
Rakefile was added to automate repetitive tasks (linting, releases, etc)
"fixeable" Foodcritic and Cookstyle bugs have been taken care of
logback.xml shipped with a ZIP file is overwritten by the cookbook to redirect knot.x output to files (custom_logback property in knotx_instance)

Fixes #14

Knotx / knotx-cookbook

knot.x 1.3 deployment #15