-
Notifications
You must be signed in to change notification settings - Fork 564
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
envoy file provider support omit_empty_values
#3426
base: master
Are you sure you want to change the base?
Conversation
/test release-notes |
omit_empty_values
// Optional. If set to true, when command operators are evaluated to null, | ||
// For text format, the output of the empty operator is changed from “-“ to an empty string. | ||
// For json format, the keys with null values are omitted in the output structure. | ||
bool omit_empty_values = 3; |
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.
by default is it is empty, isn't it difficult to distinguish which field is empty?
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.
for text, yes.
but it's useful for json.
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.
So can we only make it work for json
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.
I think it's fine to give user the option, instead of make an exception.
User can use customized separator, e.g. [%CEL(xxxxxx)%]
.
a307350
to
600974e
Compare
kindly ping @istio/technical-oversight-committee |
xref: istio/istio#54930