As discussed with @snowp in [envoyproxy/java-control-plane#87 (comment)](https://github.com/envoyproxy/java-control-plane/issues/87#issuecomment-456537248) and [envoyproxy/java-control-plane#87 (comment)](https://github.com/envoyproxy/java-control-plane/issues/87#issuecomment-457649859), adding these options will avoid the risk of having API breaking changes on the generated java code as the proto files evolve. Risk Level_: Medium Note that e.g. [envoyproxy/java-control-plane](https://github.com/envoyproxy/java-control-plane) will have to do a refactoring when they sync the proto files next time. Signed-off-by: Penn (Dapeng) Zhang <zdapeng@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4a5f85809cef13be47873483789a5a7bb64ded7c
data-plane-api(CircleCI)