-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Deprecate Hipchat Watcher actions #39160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Hipchat has ceased operating, so we are deprecating Hipchat Watcher actions to be removed in Elasticsearch 7.0. This also adds a check for hipchat account settings in elasticsearch.yml. Unfortunately with the current infrastructure we can't check the watches themselves because they're in an index.
|
Pinging @elastic/es-core-features |
|
@elasticmachine run elasticsearch-ci/1 There were some CI/version issues recently which should be resolved now. |
|
|
||
| static DeprecationIssue watcherHipchatNotificationSettingsCheck(Settings nodeSettings, PluginsAndModules plugins) { | ||
| if (nodeSettings.getByPrefix("xpack.notification.hipchat.").size() > 0) { | ||
| return new DeprecationIssue(DeprecationIssue.Level.CRITICAL, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should be a warning since it only possibly an issue. @gwbrown - thoughts on critical vs. warning ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Depends on how 7.0 behaves if you leave this setting in place. Most removed node settings are CRITICAL because Elasticsearch will refuse to start if you have unrecognized settings in elasticsearch.yml. I think that's the case here, so CRITICAL is the correct level, although I could be wrong if Watcher is doing something funny with prefix settings.
...gin/deprecation/src/main/java/org/elasticsearch/xpack/deprecation/NodeDeprecationChecks.java
Show resolved
Hide resolved
...cher/src/main/java/org/elasticsearch/xpack/watcher/actions/hipchat/HipChatActionFactory.java
Outdated
Show resolved
Hide resolved
jakelandis
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
...gin/deprecation/src/main/java/org/elasticsearch/xpack/deprecation/NodeDeprecationChecks.java
Outdated
Show resolved
Hide resolved
|
@elasticmachine run elasticsearch-ci/2 |
Hipchat has been shut down and has previously been deprecated in Watcher (elastic#39160), therefore we should remove support for these actions.
Hipchat has been shut down and has previously been deprecated in Watcher (#39160), therefore we should remove support for these actions.
Hipchat has been shut down and has previously been deprecated in Watcher (elastic#39160), therefore we should remove support for these actions.
Hipchat has been shut down and has previously been deprecated in Watcher (elastic#39160), therefore we should remove support for these actions.
Hipchat has ceased operating, so we are deprecating Hipchat Watcher actions to
be removed in Elasticsearch 7.0.
This also adds a check for hipchat account settings in elasticsearch.yml.
Unfortunately with the current infrastructure we can't check the watches
themselves because they're in an index.