Reduce deprecation logging severity for settings that are not removed in 8.0#79665
Merged
jakelandis merged 12 commits intoelastic:7.16from Oct 27, 2021
Merged
Conversation
Collaborator
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
jbaiera
approved these changes
Oct 25, 2021
Member
jbaiera
left a comment
There was a problem hiding this comment.
LGTM on the monitoring changes, though I think just one got missed
| public static final Setting.AffixSetting<Boolean> USE_INGEST_PIPELINE_SETTING = | ||
| Setting.affixKeySetting("xpack.monitoring.exporters.","use_ingest", | ||
| key -> Setting.boolSetting(key, true, Property.Dynamic, Property.NodeScope, Property.Deprecated), TYPE_DEPENDENCY); | ||
| key -> Setting.boolSetting(key, true, Property.Dynamic, Property.NodeScope, Property.Deprecated), |
Member
There was a problem hiding this comment.
I think this one should be at warning level as well?
Contributor
Author
There was a problem hiding this comment.
That setting was removed in 8.x, so it should remain critical level .
tvernum
approved these changes
Oct 26, 2021
Contributor
tvernum
left a comment
There was a problem hiding this comment.
LGTM.
In a few months we should have a conversation about what the deprecation lifecycle looks like and how setting attributes should work with that. But not now.
Contributor
Author
|
@elasticmachine update branch |
jakelandis
added a commit
that referenced
this pull request
Nov 10, 2021
Complementary to #79665 this change will reduce the deprecation logging level to WARN for (most) all non-settings that continue to exist in 8.0+.
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
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.
This commit lowers the severity for all settings from critical to warning
for all settings that are still present in 8.0.0.
releated #79107
===
Note - I have requested review from @tvernum and @jbaiera since these settings are mostly from areas for which they are familiar. Please add others for review if needed.
cc: @masseyke @rjernst @pgomulka
===
Note this settings were identified by introducing the following debug code in 8.0.0 and 7.16 and comparing the two lists. If the same setting showed up as deprecated in both 7.16 and 8.0.0 it is included in this PR. If the setting was missing in 8.0.0, no changes since the default is critical.