-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
out_es: custom http headers #8937
out_es: custom http headers #8937
Conversation
6a1537a
to
a5e26e8
Compare
a5e26e8
to
f4330ed
Compare
Hey @PettitWesley @edsiper |
f4330ed
to
3b7beb3
Compare
I'm looking to fix up the failures for CentOS 7 and Windows on 3.0 - these are down to changes outside of us (repo for CentOS and runners for Windows). They're already fixed on |
See #9415, rebase once merged. |
3b7beb3
to
346c09e
Compare
Which branch did you actually want @AndrewChubatiuk ? Might be easier to start a fresh PR :) |
346c09e
to
6ade471
Compare
6ade471
to
7f83e4e
Compare
initially I've created PR against 3.0 thought it'll be merged fast enough, but did not expect it'll take so much time. |
It's a shame we cannot just inherit the http plugin support for this directly. |
@patrick-stephens opened a fresh PR |
Added ability to set custom HTTP headers for Elasticsearch output
Enter
[N/A]
in the box, if an item is not applicable to your change.Testing
Before we can approve your change; please submit the following in a comment:
If this is a change to packaging of containers or native binaries then please confirm it works for all targets.
ok-package-test
label to test for all targets (requires maintainer to do).Documentation
fluent/fluent-bit-docs#1390
Backporting
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.