Martin Taillefer
Martin Taillefer
In order to truly support a distributed Mixer build, where templates and adapters come from far-flung repos, we need to auto-generate the nop and denier adapters. Architecturally, we can chose...
We should auto-generate a skeleton adapter suitable to bootstrap the implementation of any template type.
We must make it possible for fields to be added to a template over time in a backward compatible way. At the very least, this implies making it possible to...
The noop adapter be extended to be useful as a general-purpose testing adapter. If we aggregate the information that reaches the adapter and make it available through an API, it...
In order to allow proper multi-tenant behavior, Mixer should deliver the service name to adapters, independent of operator-level config. This avoids one service operator impersonating another. We also want to...
We need to support the use of submessages in template definitions in order to substantially increase the power and flexibility of our templating system and adapter model.
We want to add a proxy sidecar to Mixer in order to gain all the usual benefits of the sidecar, including mTLS, metrics, telemetry, quotas, etc. The essence of this...
---------- Forwarded message ---------- From: mtail Date: Mon, Jul 31, 2017 at 11:21 AM Subject: Deduping Instances To: Istio Integrations We just had this discussion during the Mixer design review...
If we want 3rd parties to create adapters for the mixer (goal for Q2), and for our own use, we must create adapter test suites that validate that the common...
The interface for REPORT adapters supports receiving an array of instances at a time, but Mixer currently only delivers single items. Given that Mixer receives reports in batches, it would...