-
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
base: main
Are you sure you want to change the base?
Conversation
…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`
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?
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.
@111andre111 Is there a reason for this or just how you implemented it at the time (either way is fine, I'm just trying to understand)?
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