...
Code Block |
---|
GET /packages/<package-name>/<version>/spec.json ex: GET /packages/PurchaseExample/4.0.0/spec.json { "spec-versionspecVersion": "1.0", "name": "PurchaseExample", "label": "Purchase History", "description": "Example Application demonstrating usage of flows, workflows, mapreduce, and services.", "author": "Cask", "org": "Cask Data Inc.", "version": "4.0.0", "created": 1234567899, "changelog": "fixed a small parsing bug", "categories": [ "examples" ], "actions": [ { "type": "create_artifact", "arguments": [ { "name": "name", "value": "PurchaseHistoryExample" }, { "name": "version", "value": "4.0.1" }, { "name": "scope", "value": "user" }, { "name": "jar", "value": "PurchaseHistoryExample-4.0.1.jar" } ] }, { "type": "create_app", "arguments": [ { "name": "name", "default": "PurchaseHistory" } ] } ] } |
...
The package spec contains some metadata about the spec itself, and a list of steps to perform on the CDAP instance. It is a JSON file of the following structure:
Code Block |
---|
{ "spec-versionspecVersion": "1.0" "actions": [ actionspec1, actionspec2, ... ] } |
...