Document possible collisions with '@custom ingest pipelines' #840
Conversation
|
A documentation preview will be available soon.
Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
There was a problem hiding this comment.
Amazing! Thanks for getting this together so quickly. Could we link to elastic/kibana#175254 as we'll be posting findings and follow-ups there?
| * `global@custom` | ||
| * `traces@custom` | ||
| * `traces-apm@custom` |
There was a problem hiding this comment.
Thanks for including some examples. I'll work on getting a full set of collision candidates (if it even exceeds this) on elastic/kibana#175254
docs/en/ingest-management/release-notes/release-notes-8.12.asciidoc
Outdated
Show resolved
Hide resolved
|
run docs-build |
|
@kpollich I hope I didn't merge this prematurely, but if there are others to add to this list, just let me know and I'll open up a new PR.
|
…849) * Document possible collisions with '@Custom ingest pipelines' * Add breaking change * Update breaking change with link to investigation issue 175254 * Change PR link to issue (cherry picked from commit 8517570) Co-authored-by: David Kilfoyle <[email protected]>
This updates the ingest pipelines section of the docs as well as the Release Notes, to warn about possible naming collisions with the new custom ingest pipelines.
Closes: #841
@kpollich I'm not sure if I've understood or explained this very well, so I'd appreciate if you can add any changes you think we need. Thanks!
Release Notes "New features" update
Release Notes "Breaking changes" update
Data Streams page update
