Skip to content

Remove hardcoded streams#1089

Merged
nikita-lavrov merged 4 commits intoelastic:masterfrom
nikita-lavrov:remove-hardcoded-streams
Mar 18, 2026
Merged

Remove hardcoded streams#1089
nikita-lavrov merged 4 commits intoelastic:masterfrom
nikita-lavrov:remove-hardcoded-streams

Conversation

@nikita-lavrov
Copy link
Contributor

Summary

Related to https://github.com/elastic/streams-program/issues/402

This PR removes all the hardcoded ingest pipelines, index and component templates from the streams challenges, since it is now possible to automatically preconfigure streams using Kibana.

@nikita-lavrov nikita-lavrov marked this pull request as ready for review March 16, 2026 12:17
@nikita-lavrov nikita-lavrov requested a review from a team March 16, 2026 14:19
Copy link
Contributor

@gbanasiak gbanasiak left a comment

Choose a reason for hiding this comment

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

LGTM


The target stream can be configured via the `stream_name` parameter (default: `logs.ecs`).

Note that this challenge requires the target stream to be preconfigured using Kibana. This can be achieved by using `esbench` to run this challenge.
Copy link
Member

Choose a reason for hiding this comment

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

Since this is a public repo, could you include details here of what would need setting up? External users won't have access to esbench

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Addressed in 9ec4c1b

@nikita-lavrov nikita-lavrov merged commit aba6aeb into elastic:master Mar 18, 2026
37 of 41 checks passed
@esbenchmachine esbenchmachine added the backport pending Awaiting backport to stable release branch label Mar 18, 2026
@esbenchmachine
Copy link
Collaborator

@nikita-lavrov
A backport is pending for this PR.
Apply all the labels that correspond to Elasticsearch minor versions expected to work with this PR, but select only from the available ones.
If intended for future releases, apply label for next minor

When a vX.Y label is added, a new pull request will be automatically created, unless merge conflicts are detected or if the label supplied points to the next Elasticsearch minor version. If successful, a link to the newly opened backport PR will be provided in a comment.

In case of merge conflicts during backporting, create the backport PR manually following the steps from README:
Final steps to complete the backporting process:

  1. Ensure the correct version labels exist in this PR.
  2. Ensure each backport pull request is labeled with backport.
  3. Review and merge each backport pull request into the appropriate version branch.
  4. Remove backport pending label from this PR once all backport PRs are merged.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport pending Awaiting backport to stable release branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants