[8.x](backport #41970) [filebeat][gcs] - Removed bucket_timeout config option and replaced bucket context with parent program context #41987
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.
Type of change
Proposed commit message
difficult to understand in its effects resulting in malconfiguration leading to processing timeouts and context cancellation, ultimately causing gaps in the ingested data. To avoid this, the bucket_timeout option has been removed. The input now uses the parent program context to handle the contexts for bucket operations.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Disruptive User Impact
Since it is a config option that has not impact on ingested data, this removal should not have any user impact.
Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs
This is an automatic backport of pull request #41970 done by [Mergify](https://mergify.com).