Skip to content

cds: remove cds metadata not-implemented tag #408

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
mattklein123 merged 1 commit into from
Jan 11, 2018
Merged

cds: remove cds metadata not-implemented tag #408

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
11 changes: 5 additions & 6 deletions api/cds.proto
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -407,12 +407,11 @@ message Cluster {
// See :ref:`base.TransportSocket<envoy_api_msg_TransportSocket>` description.
TransportSocket transport_socket = 24;

// [#not-implemented-hide:] The Metadata field can be used to provide
// additional information about the cluster. It can be used for stats,
// logging, and varying filter behavior. Fields should use reverse DNS
// notation to denote which entity within Envoy will need the information.
// For instance, if the metadata is intended for the Router filter, the filter
// name should be specified as *envoy.router*.
// The Metadata field can be used to provide additional information about the
// cluster. It can be used for stats, logging, and varying filter behavior.
// Fields should use reverse DNS notation to denote which entity within Envoy
// will need the information. For instance, if the metadata is intended for
// the Router filter, the filter name should be specified as *envoy.router*.
Metadata metadata = 25;

enum ClusterProtocolSelection {
Expand Down