Display the stability status of the Elastic Agent #17336
Merged
Conversation
This file contains 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
The Elastic Agent is currently Alpha quality software and is not ready to be used in a production environment, this commit make it obvious in the logs on startup and at enrollment. Note this doesn't use the cfgwarn helpers for two reasons: - We aren't using zap in the Elastic Agent code. - We also need to print on standout. This also add a "warn" package where the messaging can be edited once. Fixes: elastic#17328
|
Pinging @elastic/ingest-management (Team:Ingest Management) |
ruflin
approved these changes
Mar 30, 2020
ph
added a commit
to ph/beats
that referenced
this pull request
Apr 7, 2020
* Display the stability status of the Elastic Agent The Elastic Agent is currently Alpha quality software and is not ready to be used in a production environment, this commit make it obvious in the logs on startup and at enrollment. Note this doesn't use the cfgwarn helpers for two reasons: - We aren't using zap in the Elastic Agent code. - We also need to print on standout. This also add a "warn" package where the messaging can be edited once. Fixes: elastic#17328 * Add a changelog entry (cherry picked from commit b70e44b)
6 tasks
ph
added
v7.8.0
and removed
needs_backport
ph
added a commit
that referenced
this pull request
Apr 7, 2020
* Display the stability status of the Elastic Agent The Elastic Agent is currently Alpha quality software and is not ready to be used in a production environment, this commit make it obvious in the logs on startup and at enrollment. Note this doesn't use the cfgwarn helpers for two reasons: - We aren't using zap in the Elastic Agent code. - We also need to print on standout. This also add a "warn" package where the messaging can be edited once. Fixes: #17328 * Add a changelog entry (cherry picked from commit b70e44b)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 Elastic Agent is currently Alpha quality software and is not ready
to be used in a production environment, this commit make it obvious in
the logs on startup and at enrollment.
Note this doesn't use the cfgwarn helpers for two reasons:
This also add a "warn" package where the messaging can be edited once.
Fixes: #17328
What does this PR do?
Print the stability status of the Agent in the logs and in the stdout.
Why is it important?
The Elastic Agent should not be used in production and we need to be explicit about it.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Author's Checklist
How to test this PR locally
Related issues