Signed-off-by: Ryan Northey <ryan@synca.io>

Mirrored from https://github.com/envoyproxy/envoy @ eb18d71972e1f8af714d7843eb206108aad153c7

Various fixes

Signed-off-by: Matt Klein <mklein@lyft.com>

Mirrored from https://github.com/envoyproxy/envoy @ 17e815122ff53d0ac6cb2d64cdbf1bfc547bb7e8

Signed-off-by: Lizan Zhou <lizan@tetrate.io>

Mirrored from https://github.com/envoyproxy/envoy @ e136b95a6083aa9b284bb7acfe704a259c7ffa0c

Signed-off-by: Dmitri Dolguikh <ddolguik@redhat.com>

Mirrored from https://github.com/envoyproxy/envoy @ a1d3f4b0772e7bd3c5b5a3b798c00d3529787d99

* Automatically derive active protos target used in proto_format.sh from the packages with files
  annotated as active.

* Replace some sites with hardcoded v2/v3 with active/next_major_version_candidate.

* Move //docs:BUILD to //versioning:BUILD in API tree. This has already ceased to be used directly
  in the docs build, so this makes things a bit clearer.

Risk level: Low (API tooling and build only)
Testing: fix_format (mostly idempotent)

Part of #10355.

Signed-off-by: Harvey Tuch <htuch@google.com>

Mirrored from https://github.com/envoyproxy/envoy @ 4403003b9c0888ce81606a2f45fcc1da126514e7

This captures the API versioning guidelines implied by
https://docs.google.com/document/d/1xeVvJ6KjFBkNjVspPbY_PwEDHC7XPi0J5p1SqUXcCl8/edit#heading=h.xgk8xel154p


and splits apart the Envoy API and internal implementation breaking change policies.

Some of the policy decisions (e.g. not allowing vNalpha to be hand edited, how we do manual breaking
changes, etc.) have been added to these guidelines based on recent experience with protoxform and
mechanical major version upgrade work, they are not part of the original stable API versioning work.

Risk level: Low
Testing: Formatting and docs build.

Fixes #8371

Signed-off-by: Harvey Tuch <htuch@google.com>

Mirrored from https://github.com/envoyproxy/envoy @ 3801c6846a5c7bf4d230f1dad58985f2bb8bcdeb

This avoids having to list new docs protos in both docs/build.sh and
api/docs/BUILD. This technical debt cleanup is helpful in v3 proto work
to simplify collecting proto artifacts from a Bazel aspect.

Risk level: Low
Testing: docs/build.sh, visual inspection of docs.

Signed-off-by: Harvey Tuch <htuch@google.com>

Mirrored from https://github.com/envoyproxy/envoy @ b06e2b5c473b4b88e23ed66abd501e29f6bddbee

Signed-off-by: Nguyen Van Trung <trungnv@vn.fujitsu.com>

Mirrored from https://github.com/envoyproxy/envoy @ 5313bbc56e63500b48cd1c207f686cd5a9f68acf

Signed-off-by: Harvey Tuch <htuch@google.com>

Mirrored from https://github.com/envoyproxy/envoy @ 2244a56d0c475aee220dd3c5e3b1f48a384ddfa9

This PR implements the planned merge of envoyproxy/data-plane-api into envoyproxy/envoy as described in #2934 and https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/envoy-dev/KcVHFH-zQwQ

.

Risk Level: Medium (there might be unintentional breakage of dependent builds).
Testing: CI passes. There is now an additional bazel.api do_ci.sh target to build and run API tests.

Fixes #2934.

Signed-off-by: Harvey Tuch <htuch@google.com>

Mirrored from https://github.com/envoyproxy/envoy @ 1fdb6386c4bb42748530d7a9bf58ded644d77749

Signed-off-by: Constance Caramanolis <ccaramanolis@lyft.com>

Signed-off-by: Brian Pane <bpane@pinterest.com>

This is intended to capture some recent threads, it can grow as we learn
new lessons.

Signed-off-by: Harvey Tuch <htuch@google.com>

Signed-off-by: Harvey Tuch <htuch@google.com>

* Fix format.

Signed-off-by: Harvey Tuch <htuch@google.com>

Included files that should be edited in order to generate the RSTs and DOCs when a new .proto is added to the project.

Signed-off-by: Gabriel <gsagula@gmail.com>

Signed-off-by: Brian Pane <bpane@pinterest.com>

Signed-off-by: Matt Klein <mklein@lyft.com>

Signed-off-by: Harvey Tuch <htuch@google.com>

Signed-off-by: Matt Klein <mklein@lyft.com>