Cherry-pick #23277 to 7.11: [Filebeat] Use new JsonBlob type in CredentialsJSON #23303
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.
Cherry-pick of PR #23277 to 7.11 branch. Original message:
What does this PR do?
Both inputs
gcp-pubsub
andhttpjson
used[]byte
fields as part of their configurations to receive json blobs. This caused issues because the config values never get parsed properly since literal JSON strings arrived asstring
and objects as maps, causing errors similar tocan not convert 'string' into 'uint8' accessing 'auth.oauth2.google.credentials_json'
orcan not convert 'object' into 'uint8' accessing 'auth.oauth2.google.credentials_json'
.This creates a
JSONBlob
type that can be unpacked from literal json strings or from config objects into a raw json message.Checklist
- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration filesCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.