Skip to content

Conversation

@dakrone
Copy link
Member

@dakrone dakrone commented Feb 19, 2019

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.

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.
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features

@jakelandis
Copy link
Contributor

@elasticmachine run elasticsearch-ci/1
@elasticmachine run elasticsearch-ci/2
@elasticmachine run elasticsearch-ci/bwc
@elasticmachine run elasticsearch-ci/default-distro

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,
Copy link
Contributor

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 ?

Copy link
Contributor

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.

Copy link
Contributor

@jakelandis jakelandis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@dakrone
Copy link
Member Author

dakrone commented Feb 20, 2019

@elasticmachine run elasticsearch-ci/2

dakrone added a commit to dakrone/elasticsearch that referenced this pull request Feb 20, 2019
Hipchat has been shut down and has previously been deprecated in
Watcher (elastic#39160), therefore we should remove support for these actions.
@dakrone dakrone merged commit 9159b3f into elastic:6.7 Feb 20, 2019
@dakrone dakrone deleted the deprecate-hipchat-6.7 branch February 20, 2019 21:00
dakrone added a commit that referenced this pull request Feb 25, 2019
Hipchat has been shut down and has previously been deprecated in
Watcher (#39160), therefore we should remove support for these actions.
dakrone added a commit to dakrone/elasticsearch that referenced this pull request Feb 25, 2019
Hipchat has been shut down and has previously been deprecated in
Watcher (elastic#39160), therefore we should remove support for these actions.
dakrone added a commit to dakrone/elasticsearch that referenced this pull request Feb 25, 2019
Hipchat has been shut down and has previously been deprecated in
Watcher (elastic#39160), therefore we should remove support for these actions.
dakrone added a commit that referenced this pull request Feb 25, 2019
* Remove Hipchat support from Watcher (#39199)

Hipchat has been shut down and has previously been deprecated in
Watcher (#39160), therefore we should remove support for these actions.

* Add migrate note
dakrone added a commit that referenced this pull request Feb 25, 2019
* Remove Hipchat support from Watcher (#39199)

Hipchat has been shut down and has previously been deprecated in
Watcher (#39160), therefore we should remove support for these actions.

* Add migrate note
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants