[receiver/googlecloudpubsub] Remove build-in encoding #41813
Merged
Conversation
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
|
Note for approvers: I'm the code owner. |
atoulme
approved these changes
Aug 6, 2025
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.
Description
Remove build-in support for cloud_logging and raw_text encoding.
The build-in encodings now have alternative encoding extensions to replace them. The removal was announced in the readme, and with a warning at startup:
Now an decriptive error is thrown, when the encoding is still configured.
Link to tracking issue
#41812
Testing
Added tests to give good errors when removed encoding is used in config.
Documentation
Refer to alternatives in the README.