Skip to content

Fix typo (remove extra word) #18855

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.

Sign up for GitHub

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

Merged
htuch merged 1 commit into from
Nov 2, 2021
Merged

Fix typo (remove extra word) #18855

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion api/envoy/extensions/formatter/metadata/v3/metadata.proto
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ option (udpa.annotations.file_status).package_version_status = ACTIVE;
// :ref:`Metadata <envoy_v3_api_msg_config.core.v3.Metadata>` info,
// where TYPE is type of metadata (see above for supported types),
// NAMESPACE is the filter namespace used when setting the metadata, KEY is an optional
// lookup up key in the namespace with the option of specifying nested keys separated by ':',
// lookup key in the namespace with the option of specifying nested keys separated by ':',
// and Z is an optional parameter denoting string truncation up to Z characters long.
// The data will be logged as a JSON string. For example, for the following ROUTE metadata:
//
Expand Down
4 changes: 2 additions & 2 deletions docs/root/configuration/observability/access_log/usage.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -506,7 +506,7 @@ The following command operators are supported:
HTTP
:ref:`Dynamic Metadata <envoy_v3_api_msg_config.core.v3.Metadata>` info,
where NAMESPACE is the filter namespace used when setting the metadata, KEY is an optional
lookup up key in the namespace with the option of specifying nested keys separated by ':',
lookup key in the namespace with the option of specifying nested keys separated by ':',
and Z is an optional parameter denoting string truncation up to Z characters long. Dynamic Metadata
can be set by filters using the :repo:`StreamInfo <envoy/stream_info/stream_info.h>` API:
*setDynamicMetadata*. The data will be logged as a JSON string. For example, for the following dynamic metadata:
Expand Down Expand Up @@ -541,7 +541,7 @@ The following command operators are supported:
HTTP
:ref:`Upstream cluster Metadata <envoy_v3_api_msg_config.core.v3.Metadata>` info,
where NAMESPACE is the filter namespace used when setting the metadata, KEY is an optional
lookup up key in the namespace with the option of specifying nested keys separated by ':',
lookup key in the namespace with the option of specifying nested keys separated by ':',
and Z is an optional parameter denoting string truncation up to Z characters long. The data
will be logged as a JSON string. For example, for the following dynamic metadata:

Expand Down