| commit | 47e197f641e44d4fbc5c0e697e824a4c5ec76412 | [log] [tgz] |
|---|---|---|
| author | Gautham V Kidiyoor <gauthamvk@google.com> | Mon Aug 07 17:56:39 2017 +0800 |
| committer | Gautham V Kidiyoor <gauthamvk@google.com> | Mon Aug 07 18:00:00 2017 +0800 |
| tree | 7251a10233b499bf9762eca6a108d22d88f7dfc4 | |
| parent | 25a7ddf4faefcb2fdb05ec6c8c0a670f74e10d27 [diff] |
updated readme
This workspace holds an apigee adapter for Istio. It can be tested by itself, but in order to really use it you need a build of the Istio mixer that pulls it in. Instructions for that are forthcoming.
You need Bazel, just like with Istio.
make
Builds everything, and
make test
Runs the tests.
Assuming that you have built a Mixer that includes it, you can launch the mixer as follows:
First, edit testdata/global/adapters.yml to specify the organization and environment name for your Apigee adapter to use. If you deployed “edgemicro-auth” to a production org, then that is all you need. Otherwise, you can use “validationURL” to specify the base path to another proxy.
Now, launch the Mixer binary:
$MIXER_HOME/bazel-bin/cmd/server/mixs server --logtostderr --configStoreURL fs://$THIS_ROOT/testdata/configroot
(In other words the “config store URL” needs to be the absolute path of the “testdata/configroot” directory of this repo. If you get this wrong then the mixer will silently do nothing and always return “OK!”)
Once that‘s running, here’s a sample command:
$MIXER_HOME/bazel-bin/cmd/client/mixc check -a target.service=fault.svc.cluster.local \ --stringmap_attributes request.headers=apikey:SOME_VALID_API_KEY
That will send a “check” RPC to the mixer, which will respond “OK” if and only if the API key is valid.
You can also run “bazel-bin/cmd/mockserver,” which will implement the same API as edgemicro-auth, but it will do it locally so that you can test easily. With the mock server, “12345” is a valid API key.