Skip to content

Conversation

@prwhelan
Copy link
Member

In order to propagate response headers back from the proxied actions, we are directly calling the Transport actions via the NodeClient.

In order to propagate response headers back from the proxied actions, we
are directly calling the Transport actions via the NodeClient.
@prwhelan prwhelan added >refactoring :ml Machine learning Team:ML Meta label for the ML team auto-backport Automatically create backport pull requests when merged v8.19.0 v9.1.0 labels Apr 24, 2025
@prwhelan prwhelan marked this pull request as ready for review April 24, 2025 19:59
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/ml-core (Team:ML)

@prwhelan prwhelan enabled auto-merge (squash) April 25, 2025 12:47
@prwhelan prwhelan merged commit 1bce4d6 into elastic:main Apr 25, 2025
16 of 17 checks passed
@elasticsearchmachine
Copy link
Collaborator

💚 Backport successful

Status Branch Result
8.x

prwhelan added a commit to prwhelan/elasticsearch that referenced this pull request Apr 25, 2025
In order to propagate response headers back from the proxied actions, we
are directly calling the Transport actions via the NodeClient.
elasticsearchmachine pushed a commit that referenced this pull request Apr 25, 2025
In order to propagate response headers back from the proxied actions, we
are directly calling the Transport actions via the NodeClient.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-backport Automatically create backport pull requests when merged :ml Machine learning >refactoring Team:ML Meta label for the ML team v8.19.0 v9.1.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants