-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Base64-encoding/decoding parameters for Google Cloud PubSub plugins #5543
Conversation
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.
Just to be sure, the entire message is normally base64 encoded? Just double checking because I know in the pubsub push and in some synchronous pull examples only part of the JSON is encoded: https://cloud.google.com/pubsub/docs/pull#synchronous-pull
@danielnelson This is actually only setting encoded/decoded values for pubsub.Message.Data, which corresponds to the "data" field in a JSON representation of the message sent to the API. |
(cherry picked from commit dd67144)
Required for all PRs:
This enables several GCP services that can and only output base64-encoded JSON to PubSub (and thus input into Telegraf/TICK). Enabled base-64 encoded for output of metrics just because symmetry is nice and it's suggested that PubSub wants base64-encoded data no matter what.