Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

api: manifest based edge default documentation. #11151

Merged
merged 3 commits into from
May 17, 2020

Conversation

htuch
Copy link
Member

@htuch htuch commented May 11, 2020

This PR replaces #11058, taking a slightly different approach. We utilize field options to annotate fields that should be set for untrusted environments with [configure_for_untrusted_downstream, configure_for_untrusted_downstream]. Defaults are provided out-of-band, in a manifest files in docs/edge_defaults_manifest.yaml.

Protodoc glues the manifest and options together when generating field documentation, providing an additional notice for sensitive fields.

Risk level: Low (docs only).
Testing: Inspection of generated docs.

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

@@ -137,7 +138,10 @@ message Bootstrap {
Admin admin = 12;

// Optional overload manager configuration.
overload.v3.OverloadManager overload_manager = 15;
overload.v3.OverloadManager overload_manager = 15 [
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The plan is to fill out these annotations and the manifest examples for the remaining default edge examples if we agree on this approach.

This PR replaces envoyproxy#11058, taking a slightly different approach. We
utilize field options to annotate fields that should be set for
untrusted environments with [configure_for_untrusted_downstream,
configure_for_untrusted_downstream]. Defaults are provided out-of-band,
in a manifest files in docs/edge_defaults_manifest.yaml.

Protodoc glues the manifest and options together when generating field
documentation, providing an additional notice for sensitive fields.

This PR depends on envoyproxy#11108 first merging to provide the pip3 build
infrastructure.

Risk level: Low (docs only).
Testing: Inspection of generated docs.

Signed-off-by: Harvey Tuch <htuch@google.com>
@repokitteh-read-only
Copy link

CC @envoyproxy/api-shepherds: Your approval is needed for changes made to api/.
CC @envoyproxy/api-watchers: FYI only for changes made to api/.

🐱

Caused by: #11151 was synchronize by htuch.

see: more, trace.

@htuch
Copy link
Member Author

htuch commented May 14, 2020

This is now ready for general review, as the base #11108 has merged.

Copy link
Member

@mattklein123 mattklein123 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is SO SO SO amazing! 👏 👏 👏

Just some minor question/comments but suggest we ship and iterate. Thank you!

/wait

@@ -0,0 +1,56 @@
# Validate a YAML fragment against an Envoy API proto3 type.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is so, so, so close to the sphinx plugin. ;)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right, @dmitri-d is working on the Sphinx RST plugin side of this at the moment.

tools/protodoc/protodoc.py Outdated Show resolved Hide resolved
tools/protodoc/protodoc.py Outdated Show resolved Hide resolved
Copy link
Member

@mattklein123 mattklein123 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!

@htuch htuch merged commit 31128e7 into envoyproxy:master May 17, 2020
@htuch htuch deleted the config-validation branch May 17, 2020 19:32
spenceral added a commit to spenceral/envoy that referenced this pull request May 20, 2020
Signed-off-by: Spencer Lewis <slewis@squareup.com>

* master: (33 commits)
  docs: break release notes into categories (envoyproxy#11217)
  admin: extract more handlers to separate classes  (envoyproxy#11258)
  Load reporting service documentation  (envoyproxy#10962)
  http: testing 304-with-body behavior (envoyproxy#11261)
  fixing typos and breaking link issues (envoyproxy#11270)
  devex: initial commit of devcontainer setup (envoyproxy#11207)
  security: update policy for fix/disclosure SLOs. (envoyproxy#11243)
  http: fixing CONNECT to not advertise chunk encoding. (envoyproxy#11245)
  docs: update upstream network filters description (envoyproxy#11231)
  deps: update datadog tracer to v1.1.5 (envoyproxy#11253)
  test: Fix missing instantiation of parameterized tests. (envoyproxy#11247)
  fix go mirror when no changes (envoyproxy#11249)
  docs: host_rewrite -> host_rewrite_literal (envoyproxy#11229)
  wasm: update V8 to v8.3.110.9. (envoyproxy#11233)
  tls: update BoringSSL to 107c03cf (4103). (envoyproxy#11232)
  bazelci: always exclude nocoverage tag in coverage config (envoyproxy#11226)
  ci: save api revision in go-control-plane (envoyproxy#11220)
  build: fix cares build (envoyproxy#11225)
  stats: Pre-allocate codec stats for http1 and http2 (envoyproxy#11135)
  api: manifest based edge default documentation. (envoyproxy#11151)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants