| commit | 6dc2907308f73dca7ee8edfb653bc54437e6ae45 | [log] [tgz] |
|---|---|---|
| author | Matthew Dobson <mdobson@apigee.com> | Wed Jan 11 20:22:45 2017 -0500 |
| committer | Scott Ganyo <scott@ganyo.com> | Wed Jan 11 17:22:45 2017 -0800 |
| tree | eef4566e2b962905504d11254aca42b0808c7bc2 | |
| parent | 17b4d48750455aef523acfc21e38ee21823b77c8 [diff] |
Updated to allow for multiple bundles to stood up with standalone. (#4) * Updated to allow for multiple bundles to stood up with standalone. * Removing the glide.lock file to get rid of conflicts. * Fixing issue with glide.lock
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 -bundle option, the server will start using a clean database that contains only the deployment bundle specified.
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.