Describes the structure of messages generated by Istio analyzers.
AnalysisMessageBase describes some common information that is needed for all messages. All information should be static with respect to the error code.
AnalysisMessageWeakSchema is the set of information that’s needed to define a weakly-typed schema. The purpose of this proto is to provide a mechanism for validating istio/istio/galley/pkg/config/analysis/msg/messages.yaml to make sure that we don’t allow committing underspecified types.
GenericAnalysisMessage is an instance of an AnalysisMessage defined by a schema, whose metaschema is AnalysisMessageWeakSchema. (Names are hard.) Code should be able to perform validation of arguments as needed by using the message type information to look at the AnalysisMessageWeakSchema and examine the list of args at runtime. Developers can also create stronger-typed versions of GenericAnalysisMessage for well-known and stable message types.
InternalErrorAnalysisMessage is a strongly-typed message representing some error in Istio code that prevented us from performing analysis at all.
A unique identifier for the type of message. Name is intended to be human-readable, code is intended to be machine readable. There should be a one-to-one mapping between name and code. (i.e. do not re-use names or codes between message types.)
The values here are chosen so that more severe messages get sorted higher, as well as leaving space in between to add more later
invalid, but included for proto compatibility for 0 values