Drop project-id from threadcontext for CCS#136664
Merged
tvernum merged 2 commits intoelastic:mainfrom Oct 16, 2025
Merged
Conversation
When making a request to a remote cluster, we don't want to include
the current project-id ("X-Elastic-Project-Id") header in the thread
context that we send to the remote cluster because the current
project-id is not relevant to the thread context for the remote
execution.
tvernum
added
>bug
:Security/Authorization
Collaborator
|
Pinging @elastic/es-security (Team:Security) |
Collaborator
|
Hi @tvernum, I've created a changelog YAML for you. |
elasticsearchmachine
added
the
serverless-linked
tvernum
added
v9.2.1
auto-backport
Collaborator
💔
|
| Status | Branch | Result |
|---|---|---|
| ❌ | 9.1 | |
| ❌ | 9.2 |
9.2
9.1
tvernum
added a commit
to tvernum/elasticsearch
that referenced
this pull request
Oct 16, 2025
When making a request to a remote cluster, we don't want to include
the current project-id ("X-Elastic-Project-Id") header in the thread
context that we send to the remote cluster because the current
project-id is not relevant to the thread context for the remote
execution.
Backport of: elastic#136664
elasticsearchmachine
pushed a commit
that referenced
this pull request
Oct 16, 2025
When making a request to a remote cluster, we don't want to include
the current project-id ("X-Elastic-Project-Id") header in the thread
context that we send to the remote cluster because the current
project-id is not relevant to the thread context for the remote
execution.
Backport of: #136664
Co-authored-by: Johannes Fredén <109296772+jfreden@users.noreply.github.com>
Kubik42
pushed a commit
to Kubik42/elasticsearch
that referenced
this pull request
Oct 16, 2025
When making a request to a remote cluster, we don't want to include
the current project-id ("X-Elastic-Project-Id") header in the thread
context that we send to the remote cluster because the current
project-id is not relevant to the thread context for the remote
execution.
tvernum
added a commit
to tvernum/elasticsearch
that referenced
this pull request
Oct 16, 2025
When making a request to a remote cluster, we don't want to include
the current project-id ("X-Elastic-Project-Id") header in the thread
context that we send to the remote cluster because the current
project-id is not relevant to the thread context for the remote
execution.
Backport of: elastic#136664,elastic#136675
elasticsearchmachine
pushed a commit
that referenced
this pull request
Oct 17, 2025
When making a request to a remote cluster, we don't want to include
the current project-id ("X-Elastic-Project-Id") header in the thread
context that we send to the remote cluster because the current
project-id is not relevant to the thread context for the remote
execution.
Backport of: #136664,#136675
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
When making a request to a remote cluster, we don't want to include the current project-id ("X-Elastic-Project-Id") header in the thread context that we send to the remote cluster because the current project-id is not relevant to the thread context for the remote execution.