[BeatsCM] add deprecation message#48097
Closed
mattapperson wants to merge 7 commits intoelastic:masterfrom
Closed
Conversation
Contributor
💚 Build Succeeded |
Contributor
Author
|
@elasticmachine merge upstream |
Contributor
💚 Build Succeeded |
Contributor
|
We decided to use a slightly different message in the docs to get around making the statement version-specific. Here's what we used. Not sure if you want to align the messaging in Kibana. I think the deprecation statement works fine, too. We have ceased development on Beats central management and |
Contributor
Author
|
@elasticmachine merge upstream |
dedemorton
reviewed
Oct 24, 2019
Co-Authored-By: DeDe Morton <dede.morton@elastic.co>
Contributor
💔 Build Failed |
Contributor
💚 Build Succeeded |
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
The beta feature "Beats Central Management" has been deprecated for some time while we work on a replacement feature that takes an entirely different method. Communication regarding this deprecation has been non-ideal, so to ensure customers are aware of the upcoming switch, we are adding this messaging directly in the UI.