-
Notifications
You must be signed in to change notification settings - Fork 29
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
Support node metadata in aggregation rules #125
Labels
Comments
Merged
jyotimahapatra
pushed a commit
that referenced
this issue
Nov 19, 2020
This PR adds a matcher for node metadata fields. This is for #125. Similarly to #137, we encode the node metadata information required in the aggregation rules in a pair of protos: (1) NodeMetadataMatch, and (2) NodeMetadataAction, the former related to the matching process, whereas the latter has to do with the formation of the fragment. Envoy's node metadata is an opaque struct of type google.protobuf.Struct, which basically represents a dictionary of strings to Value. This PR adds support for 3 of the 6 values: string, bool, and a nested struct of Value. The support for these other types is going to be added in separate PRs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Support the freeform 'metadata' field in the aggregation rules.
API: https://www.envoyproxy.io/docs/envoy/latest/api-v2/api/v2/core/base.proto
The text was updated successfully, but these errors were encountered: