We only generate this for some resources and not others, and no one has
complained -- so there doesn't seem to be much value in maintaining
this, but it provides a lot of boilerplate.
Rather than "fixing" it to be used for all types, seems better to just
drop this. We already have the schema as proto and OpenAPI (via CRD).
* Move istio/proxy protos into istio/api
Fixes https://github.com/istio/istio/issues/35210.
This does two things:
* Move some protos we have in istio/istio that are manually generating
the go protos, using an outdated protobuf library and outdated proto.
* Move some protos we have in istio/proxy that are not generating any go
protos at all.
A next step will be to have istio/istio import these go libraries, and
istio/proxy to import these as proto_libraries.
* add README
* Add initial Telemetry API definition
* fix names and comments
* Rename TracingConfig to Tracing
* Remove TelemetryProviders and consolidate to just Tracing providers
* add new extension providers to oneof
* Remove providers from telemetry API
* Add release note
* Address comments
* Add back providers, remove match, simplify Trace API
* Collapse TracingRule into Tracing and remove deprecations in ProxyConfig
* Move from address to service + port in providers
* Remove exclude_mesh_tags
* Revert to boolean control of span reporting
* Cleanup documentation
* Replace subdomain with telemetry type
https://docs.buf.build/
Buf is the successor to https://github.com/uber/prototool which we
already use for linting.
This dramatically simplifies our Makefiles, which are both extremely
complicated and have led to numerous bugs historically, such as
https://github.com/istio/api/issues/1678.
This will make changes to the generation much simpler as well. For
example, to migrate to gogo protobuf, we will just need to change `gogo`
-> `go` in one location, rather than trying to wrangle 500 lines of
Makefiles. Additionally, its quite a bit faster - the whole proto stuff
is done in <1s now.
zirain