-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Allow headers config to propagate in callAsCurrentUser
#34610
Conversation
Pinging @elastic/kibana-platform |
💚 Build Succeeded |
💔 Build Failed |
💔 Build Failed |
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.
Looking good, just want to see the tests broken up a bit to make it clearer what the expected behavior is.
retest |
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.
LGTM
Pinging @elastic/kibana-stack-services |
💔 Build Failed |
💔 Build Failed |
💔 Build Failed |
💔 Build Failed |
💔 Build Failed |
💔 Build Failed |
💚 Build Succeeded |
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.
lgtm on green CI
💔 Build Failed |
💚 Build Succeeded |
Allow
clientParams.headers
config to propagate incallAsCurrentUser
. The current implementation overrides the object wheneverthis.headers
is set which provides inconsistent and undesired behavior.This PR also adds a header when hitting Telemetry monitoring indexes. In case we want to filter / track those es queries from cloud billing. I added this in the same PR since the change is very trivial and I introduced the fix for this use-case.
Adds the following header to the ES query when telemetry hits monitoring indexes to gather usage data.
More context:
https://github.com/elastic/kibana/pull/28344/files#r257774129
CC @alexfrancoeur, @azasypkin