Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions installation/upgrade-notes.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,18 @@ Note: release notes will be prepared in advance of a Git tag for a release so an
The tag drives the overall binary release process so release binaries (containers/packages) will appear after a tag and its associated release note.
This allows users to expect the new release binary to appear and allow/deny/update it as appropriate in their infrastructure.

## Fluent Bit v4.0+

By default, configuration files use YAML syntax and the `.yaml` file extension.

You may need to update your custom deployments to either use YAML configuration files
or switch back to using legacy configuration in the arguments to the Fluent Bit binary.

In Linux environments, you must override the systemd unit to specify `-c <legacy config file>`.

Similarly, in Windows and macOS container environments, the default launch command uses YAML configuration files
by default.
Comment on lines +21 to +22

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Remove redundant "by default".

The phrase "by default" appears twice in this sentence and is also redundant with line 14, which already establishes that YAML is the default format. This reduces clarity.

✏️ Proposed fix to remove redundancy
-Similarly, in Windows and macOS container environments, the default launch command uses YAML configuration files
-by default.
+Similarly, in Windows and macOS container environments, the default launch command uses YAML configuration files.

Or alternatively, for better parallel structure with the Linux guidance:

-Similarly, in Windows and macOS container environments, the default launch command uses YAML configuration files
-by default.
+In Windows and macOS container environments, the default launch command uses YAML configuration files.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
Similarly, in Windows and macOS container environments, the default launch command uses YAML configuration files
by default.
Similarly, in Windows and macOS container environments, the default launch command uses YAML configuration files.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@installation/upgrade-notes.md` around lines 21 - 22, Remove the redundant "by
default" from the sentence that currently reads "Similarly, in Windows and macOS
container environments, the default launch command uses YAML configuration files
by default." — change it to "Similarly, in Windows and macOS container
environments, the default launch command uses YAML configuration files."
Alternatively, if you want parallel structure with the Linux guidance, rephrase
to "Similarly, in Windows and macOS container environments, use YAML
configuration files for the default launch command."


## Fluent Bit v1.9.9

The `td-agent-bit` package is no longer provided after this release.
Expand Down