out_s3: fix the error message of total_file_size limit when use_put_object is enabled #10470
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.
Background
This PR fixes a bug in the S3 Output plugin related to the
total_file_size
error message.Although the actual limit is 1GB (
MAX_FILE_SIZE_PUT_OBJECT
), the error message still incorrectly states it as "50M".This PR updates the error message to reflect the current limit, following the same approach used for
MAX_FILE_SIZE
to ensure consistency across the codebase.Testing
Below is an excerpt from the output of
run_code_analysis.sh
:Fluent Bit is licensed under Apache 2.0, by submitting this pull request I understand that this code will be released under the terms of that license.