commit | 809d44c812ab2a3816239608b7554e5fb80abbc6 | [log] [tgz] |
---|---|---|
author | Scott Ganyo <scott@ganyo.com> | Thu Oct 27 09:30:09 2016 -0700 |
committer | Scott Ganyo <scott@ganyo.com> | Thu Oct 27 09:30:09 2016 -0700 |
tree | 0d46139177035457f6dc44ce9b2f7243eb8f8a95 | |
parent | c85c0f5e83aee56725e525133c5d70dc85db8a16 [diff] |
Rewrite the /current API logic to fix errors and match the spec
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/current
- retrieve current deploymentPOST /deployments/{id}
- update specified deploymentFirst, 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 -manifest
option, the server will start using a clean database that contains only the deployment manifest specified.
Once the process is running, you should be able to manually give the plugin's API a whirl...
curl -i localhost:9000/deployments/current curl -i -X POST localhost:9000/deployments/entityId -d '{ "status": "SUCCESS" }'
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.