[Website]: Misleading guidance regarding creating a @custom ingest pipeline and need of rollover #1764
Description
Type of issue
Misleading info
What documentation page is affected
https://www.elastic.co/docs/reference/fleet/data-streams-pipeline-tutorial
What happened?
Most Fleet integrations follow the pattern where the bundled ingest pipeline calls a set of @custom ingest pipelines by default.
Therefore the rollover is not really a necessary step.
In the header, we mark it as "optional".
Problematic section from @jeanfabrice :
Roll over the data stream (optional)
For pipeline changes to take effect immediately, you must roll over the data stream. If you do not, the changes will not take effect until the next scheduled roll over. Select Apply now and rollover.
- There is no need to rollover, assuming the default integration's pipeline is natively calling the (existing or non-existing) custom pipeline
- There is no such "Apply now and rollover" button (Maybe this changed in recent versions?)
Additional info
Except if we're missing some edge case, the rollover would be completely un-necessary. Maybe this should be double checked by a Fleet dev/engineer.