Cherry-pick #24907 to 7.x: Restart process on output change #25160
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-pick of PR #24907 to 7.x branch. Original message:
What does this PR do?
This PR adds an option to specify in a spec file behavior on output change as sometimes new output definition is not reloaded correctly on beats side.
Endpoint reloads output ok, fleet server does not reload output at all but we agreed to fix it on server side.
Why is it important?
#23596
#24538
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.