-
Notifications
You must be signed in to change notification settings - Fork 269
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
docs: /runtime_modify admin endpoint docs #557
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks. Might need to be modified depending on what we decide to do with viewing override values via /runtime
. Also needs format fix.
Formatted. Left comments about viewing runtime on the envoy PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, doc suggestion added.
:ref:`/runtime admin endpoint <operations_admin_interface_runtime>`. Values can be modified and | ||
added at the :ref:`/runtime_modify admin endpoint <operations_admin_interface_runtime_modify>`. If | ||
runtime is not configured, an empty provider is used which has the effect of using all defaults | ||
built into the code, except for any values added via `/runtime_modify`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe this could merit an additional ::attention:: comment on the dangers of the admin endpoint. We're now exposing a lot more knobs via this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1, I would just let people know that admin values can get tweaked via the endpoint and that they need to pay special attention to admin security (paraphrasing).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just a few fixups needed. Thanks!
docs/root/operations/admin.rst
Outdated
@@ -186,6 +186,8 @@ The fields are: | |||
v0.0.4 format. This can be used to integrate with a Prometheus server. Currently, only counters and | |||
gauges are output. Histograms will be output in a future update. | |||
|
|||
.. _operations_admin_interface_runtime: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add some more expansive docs here on the new JSON output?
docs/root/intro/version_history.rst
Outdated
@@ -3,6 +3,7 @@ Version history | |||
|
|||
1.6.0 | |||
===== | |||
* admin: added :ref:`/runtime_modify endpoint <operations_admin_interface_runtime_modify>` to add or change runtime values |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please move up to 1.7.0 section.
:ref:`/runtime admin endpoint <operations_admin_interface_runtime>`. Values can be modified and | ||
added at the :ref:`/runtime_modify admin endpoint <operations_admin_interface_runtime_modify>`. If | ||
runtime is not configured, an empty provider is used which has the effect of using all defaults | ||
built into the code, except for any values added via `/runtime_modify`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1, I would just let people know that admin values can get tweaked via the endpoint and that they need to pay special attention to admin security (paraphrasing).
PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, thanks.
Plus a release note