| commit | b7306a6883f9d4ad1e1d0c60f71f903d190c1bbc | [log] [tgz] |
|---|---|---|
| author | Scott Ganyo <scott@ganyo.com> | Thu Jan 12 10:45:12 2017 -0800 |
| committer | Scott Ganyo <scott@ganyo.com> | Thu Jan 12 10:47:29 2017 -0800 |
| tree | d87d33267343ea903641a756f3545fd5d0781675 | |
| parent | 6dc2907308f73dca7ee8edfb653bc54437e6ae45 [diff] |
Fix issue with JSON formatting, redo main cmd to simply accept a file containing expected deployments
This core plugin for apid responds to apidApigeeSync events and publishes an API that allows clients to deploy and update a locally configured gateway.
This plugin simply tracks counters based on called URIs:
GET /deployments/ - retrieve current deploymentPOST /deployments/ - update deploymentsSee apidGatewayDeploy-api.yaml for full spec.
First, install prerequisites:
glide install
To run an apid test instance with just this plugin installed, change to the cmd/apidGatewayDeploy folder. From here, you may create an executable with:
go build
Alternatively, you may run without creating an executable with:
go run main.go
Command line options:
If you use the -deployments option, the server will start using a clean database that contains only the deployments contained in the file specified.
The file should be the JSON for an array of deployments. JSON format is:
[
{
"id": "",
"scopeId": "",
"created": "",
"createdBy": "",
"updated": "",
"updatedBy": "",
"configuration": {
"key": "value"
},
"bundleConfiguration": {
"key": "value"
},
"displayName": "",
"uri": ""
}
]
Notes:
Once the process is running, you should be able to manually give the plugin's API a whirl...
curl -i localhost:9000/deployments/
curl -i -X POST localhost:9000/deployments -d '{ ... }'
The following may be interesting env vars for configuration:
To run the tests, just run:
go test
To generate coverage, you may run:
./cover.sh
Then open cover.html with your browser to see details.