Support for bytes encoding for "gnmi" input plugin#7938
Merged
ssoroka merged 1 commit intoinfluxdata:masterfrom Nov 2, 2020
Merged
Support for bytes encoding for "gnmi" input plugin#7938ssoroka merged 1 commit intoinfluxdata:masterfrom
ssoroka merged 1 commit intoinfluxdata:masterfrom
Conversation
Contributor
Author
|
Hi @danielnelson, I am not sure if you are the intended reviewer for that domain? |
ssoroka
approved these changes
Oct 28, 2020
Contributor
ssoroka
left a comment
There was a problem hiding this comment.
This is great. There's also an ASCII encoding. should we be supporting that, too?
Contributor
Author
|
Thanks for the approval.
Technically ascii should be allowed to be specified as well
…On Wed, 28 Oct 2020, 22:56 Steven Soroka, ***@***.***> wrote:
***@***.**** approved this pull request.
This is great. There's also an ASCII encoding. should we be supporting
that, too?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#7938 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABLKV5MOHWMT4D7GP7OFYDDSNCHR3ANCNFSM4PUGXMFQ>
.
|
Contributor
|
looks like at the moment ascii is not part of the docs and will complain that it's not a supported type. |
Contributor
Author
|
Correct, it needs to be added in the same fashion as this PR adds `bytes`
support.
…On Thu, Oct 29, 2020 at 4:08 PM Steven Soroka ***@***.***> wrote:
looks like at the moment ascii is not part of the docs and will complain
that it's not a supported type.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#7938 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABLKV5IJBLCUWQGK7YPF4YLSNGAORANCNFSM4PUGXMFQ>
.
|
Contributor
Author
|
@ssoroka can we merge this one and address ASCII later? Thank you |
Contributor
|
Merged. Thank you! |
ssoroka
pushed a commit
that referenced
this pull request
Nov 13, 2020
(cherry picked from commit 68a4f18)
arstercz
pushed a commit
to arstercz/telegraf
that referenced
this pull request
Mar 5, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Required for all PRs:
Purpose of the PR
This PR adds support for
bytesencoding for the gNMI messages as per 2.3.2 of gNMI specification.The code already had a support for
bytesencoded values, it was just not allowed to specify this encoding in the appropriate check before.The only changes made to the plugin were to allow to specify
bytesas theencoding.Example
Config file:
Output: