-
Notifications
You must be signed in to change notification settings - Fork 154
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
Add per request functionality to add HTTP request headers #756
Open
111andre111
wants to merge
14
commits into
elastic:main
Choose a base branch
from
111andre111:main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
…y` using `setExtraHeaders()`
…multiple entries
…h per-request headers (`currentRestEntry`)
…ng Kibana REST queries/lifecycle
…ng Elasticsearch REST queries/lifecycle
…ng Logstash REST queries/lifecycle
…like `elastic-api-version`
pickypg
reviewed
Oct 10, 2024
RestEntry restEntry = new RestEntry(name, subdir, extension, retry, url, showErrors, pageableFieldName, spaceAware); | ||
|
||
// Logic for handling extra-headers, if they exist, after RestEntry is created | ||
if (info.containsKey("extra-headers")) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a downside to just extracting the headers during creation, like we do with spaceAware
for example?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Feature statement
Adds functionality to configure headers on a per request statement
Syntax example:
Checklist
config/diags.yml
from Add support for additional headers to DiagnosticService #519 still workse.g.
{kibana|elastic|logstash}-rest.yaml
overwrite the global header functionalityFixes #657