api/config: deprecate build_version in DiscoveryRequest. (#9620)
This is a followup to #9301, where it was not possible to deprecate a field on DiscoveryRequest as we were previously assuming identical v2/v3 transport protocols. After this deprecation, build_version can't appear in v3 messages, and we need to convert back to a true v2 DiscoveryRequest prior to JSON serializing for REST. There's more work to be done in the future, when we add new v3-only fields, but this should work for 1.13.0. Future work tracked at https://github.com/envoyproxy/envoy/issues/9619. Risk level: Low Testing: coverage of the behaviors for both gRPC and REST config sources is provided by api_version_integration_test (failing previously as soon as build_version was deprecated). Fixes #9604 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 0ee6212b02bdab7b3d66e868449ac93556e63118master-ci-test
parent
ab80ff8c19
commit
6467390343
2 changed files with 6 additions and 10 deletions
Loading…
Reference in new issue