old_mixer_repo
old_mixer_repo copied to clipboard
istio
Deprecated home of Istio's Mixer and its adapters, now in istio/istio's mixer dir
Adapter developers mainly just look at the documentation associated with the generated interface in the generated go file. Consider having a constant or a Comment generated in that file that...
Mixer attributes today are all materialized when they are defined. This is specifically the case where an attribute is the result of evaluation of a function, like in case of...
Mixer configuration system enforces type safety at config ingestion time. The effectiveness of the type checks depend on having typed attributes. Isio vocabulary defines a set of typed attributes. However...
Once we've deleted all legacy adapters, we need to systematically purge the Mixer codebase from all legacy code/types/etc. We also have a few things to rename (adapter.BuilderInfo -> adapter.Info among...
It's desirable to pass a per-request Env object for use by adapters. This would let Mixer fine-tune things like logging output for the request. The env can be passed in...
For APAs and for other adapters too, we need a mechanism to figure out what input fields did the adapter used within a scope of a given request. This information...
We need to allow template developers to make breaking changes to their template via some versioning mechanism.
we'd like to enable systematic support to allow submessages to be instantiated inline in the YAML, or via reference. Via reference allows the same submessage to be reused in multiple...
This is a subtask from other top level bug: #534 * validation that generation of an attribute value is not occurring in multiple places (proxy-mixer, mixer APAs, etc.)
We want Mixer to be able to ingest and manipulate tracing data, so we need a generic template to carry tracing data.