-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Manifest based documentaton extensions #11085
Labels
Comments
This was referenced May 6, 2020
htuch
added a commit
to htuch/envoy
that referenced
this issue
May 7, 2020
This was added before we started annotating fields missing implementations. Fixed with a [#not-implemented-hide:] annotations for now, the plan is to move things like this to envoyproxy#11085 when it lands. Signed-off-by: Harvey Tuch <[email protected]>
htuch
added a commit
that referenced
this issue
May 7, 2020
This was added before we started annotating fields missing implementations. Fixed with a [#not-implemented-hide:] annotations for now, the plan is to move things like this to #11085 when it lands. Signed-off-by: Harvey Tuch <[email protected]>
mattklein123
pushed a commit
to envoyproxy/data-plane-api
that referenced
this issue
May 7, 2020
This was added before we started annotating fields missing implementations. Fixed with a [#not-implemented-hide:] annotations for now, the plan is to move things like this to envoyproxy/envoy#11085 when it lands. Signed-off-by: Harvey Tuch <[email protected]> Mirrored from https://github.com/envoyproxy/envoy @ a250a871571f18dffd13732da83cbd4a677b1f03
htuch
added a commit
to htuch/envoy
that referenced
this issue
May 7, 2020
Provide an Envoy build system styled way of loading arbitrary pip3 packages as py_{library,binary} dependencies. Part of envoyproxy#11085 (to fetch PyYAML). Risk level: Low (build system) Testing: Manual validation that the test utility loads PyYAML at the correct version (different to my system version). Signed-off-by: Harvey Tuch <[email protected]>
lizan
pushed a commit
that referenced
this issue
May 12, 2020
Provide an Envoy build system styled way of loading arbitrary pip3 packages as py_{library,binary} dependencies. Part of #11085 (to fetch PyYAML). Risk level: Low (build system) Testing: Manual validation that the test utility loads PyYAML at the correct version (different to my system version). Signed-off-by: Harvey Tuch <[email protected]>
htuch
added a commit
to htuch/envoy
that referenced
this issue
May 29, 2020
Adding API annotations and manifest entries to match https://www.envoyproxy.io/docs/envoy/latest/configuration/best_practices/edge#best-practices-edge. Risk level: Low (API/docs only change) Testing: Docs build and inspection. Fixes envoyproxy#11085 Signed-off-by: Harvey Tuch <[email protected]>
htuch
added a commit
that referenced
this issue
Jun 9, 2020
Adding API annotations and manifest entries to match https://www.envoyproxy.io/docs/envoy/latest/configuration/best_practices/edge#best-practices-edge. Risk level: Low (API/docs only change) Testing: Docs build and inspection. Fixes #11085 Signed-off-by: Harvey Tuch <[email protected]>
songhu
pushed a commit
to songhu/envoy
that referenced
this issue
Jun 25, 2020
Adding API annotations and manifest entries to match https://www.envoyproxy.io/docs/envoy/latest/configuration/best_practices/edge#best-practices-edge. Risk level: Low (API/docs only change) Testing: Docs build and inspection. Fixes envoyproxy#11085 Signed-off-by: Harvey Tuch <[email protected]>
yashwant121
pushed a commit
to yashwant121/envoy
that referenced
this issue
Jul 24, 2020
Adding API annotations and manifest entries to match https://www.envoyproxy.io/docs/envoy/latest/configuration/best_practices/edge#best-practices-edge. Risk level: Low (API/docs only change) Testing: Docs build and inspection. Fixes envoyproxy#11085 Signed-off-by: Harvey Tuch <[email protected]> Signed-off-by: yashwant121 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As per #11058 (comment), it would be ideal to be able to augment API field documentation with things such as:
The solution is to have a proxy manifest file that acts as a map from API field to additional information. This will be glued by
protodoc
(for Envoy at least) in to the final end user docs.The text was updated successfully, but these errors were encountered: