old_mixer_repo
old_mixer_repo copied to clipboard
Deprecated home of Istio's Mixer and its adapters, now in istio/istio's mixer dir
We've discussed previously in a few context the need to allow operators to augment instances with custom data, and in fact the general need to let operators mutate existing instances...
The istio builder image (`gcr.io/istio-io/istio-builder:0.1`) has an old (no longer working with our codebase) version of bazel installed. We should get a new image with the proper version of bazel,...
We need to introduce generic support to let operator indicate that individual adapter should fail open or close. When an adapter is marked to fail open, Mixer will automatically swallow...
It seems we'll be needing a mechanism to keep some standard per-adapter config that Mixer can use with all adapters. We don't have room to store such configuration in our...
We need to handle adapter failures in a systematic way. Whether an adapter panics, always returns errors, or constantly times out, we need to have a clear detection, tracking, and...
We need to detect if an adapter has stop being responsive by tracking execution timeouts. Ideally, we maintain per-adapter configuration state with the max execution time allowed for calls into...
We want to make config error reporting to be top notch. Error reports should be precise (file, line #) and descriptive, with ideally suggestions to the operator on how to...
The Mixer currently exposes an API intended for use by the proxy (the intermediated API). We wish to allow services to directly call Mixer in order to do: - Custom...
We want the ability to dynamically inspect and control a running instance of Mixer and other Istio components. This for things like inspecting counters, controlling log levels, tweaking various parameters,...