out_es: custom http headers #8937
Closed
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
AndrewChubatiuk
requested review from
PettitWesley,
celalettin1286,
edsiper,
fujimotos,
koleini,
leonardo-albertovich,
niedbalski and
patrick-stephens
as code owners
AndrewChubatiuk
force-pushed
the
out-es-custom-http-headers
branch
2 times, most recently
from
6a1537a to
a5e26e8
Compare
AndrewChubatiuk
changed the title
AndrewChubatiuk
force-pushed
the
out-es-custom-http-headers
branch
from
a5e26e8 to
f4330ed
Compare
1 task
Contributor
Author
|
Hey @PettitWesley @edsiper |
AndrewChubatiuk
force-pushed
the
out-es-custom-http-headers
branch
from
f4330ed to
3b7beb3
Compare
AndrewChubatiuk
had a problem deploying
to
pr
GitHub Actions
Failure
AndrewChubatiuk
had a problem deploying
to
pr
GitHub Actions
Failure
AndrewChubatiuk
had a problem deploying
to
pr
GitHub Actions
Failure
Collaborator
|
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 |
Collaborator
|
See #9415, rebase once merged. |
AndrewChubatiuk
force-pushed
the
out-es-custom-http-headers
branch
from
3b7beb3 to
346c09e
Compare
Collaborator
|
Which branch did you actually want @AndrewChubatiuk ? Might be easier to start a fresh PR :) |
AndrewChubatiuk
force-pushed
the
out-es-custom-http-headers
branch
from
346c09e to
6ade471
Compare
AndrewChubatiuk
force-pushed
the
out-es-custom-http-headers
branch
from
6ade471 to
7f83e4e
Compare
Contributor
Author
|
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. |
Collaborator
|
It's a shame we cannot just inherit the http plugin support for this directly. |
Contributor
Author
|
@patrick-stephens opened a fresh PR |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
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-testlabel 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.