Skip to content

Conversation

@nielsbauman
Copy link
Contributor

Instead of implicitly relying on the IngestService to resolve the project ID, the simulate pipeline request should do this and pass the project ID explicitly.

Instead of implicitly relying on the `IngestService` to resolve the
project ID, the simulate pipeline request should do this and pass the
project ID explicitly.
@nielsbauman nielsbauman added >non-issue :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP Team:Data Management Meta label for data/management team v9.1.0 labels Mar 4, 2025
@nielsbauman nielsbauman requested a review from a team March 4, 2025 17:41
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-data-management (Team:Data Management)

Copy link
Member

@ywangd ywangd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@nielsbauman nielsbauman merged commit 10e23b3 into elastic:main Mar 5, 2025
17 checks passed
@nielsbauman nielsbauman deleted the mp-simulate-pipeline branch March 5, 2025 07:30
georgewallace pushed a commit to georgewallace/elasticsearch that referenced this pull request Mar 11, 2025
Instead of implicitly relying on the `IngestService` to resolve the
project ID, the simulate pipeline request should do this and pass the
project ID explicitly.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP >non-issue Team:Data Management Meta label for data/management team v9.1.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants