-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Add "deprecated" flag to query runners (and alert destinations) #3972
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
Add "deprecated" flag to query runners (and alert destinations) #3972
Conversation
Related #3805. |
…uery runners when adding a new data source
…ted alert destinations when adding a new alert destination
} | ||
|
||
|
||
@deprecated() |
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.
@arikfr not sure you actually wanted to deprecate this (and the URL data source) as part of this PR, so let me know if you want me to revert this commit.
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.
No, it's cool. We do need to update the docs about the URL data source though.
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.
The page currently mixes JSON
and URL
and feels like it might need a slight rewrite (or some good chunks related to URL
removed). WDYT @susodapop?
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.
👌
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.
👍
…edash#3972) * add a deprecated flag to query runners and show only non-deprecated query runners when adding a new data source * add a deprecated flag to alert destinations and show only non-deprecated alert destinations when adding a new alert destination * add a deprecated() decorator for a more succint way to deprecate * deprecate URL query runner and HipChat alert destination * use class properties instead of class methods for deprecation * I <3 newlines
Deprecated Query Runners/Alert Destinations will not show up in the list of available types when creating a new one, but will remain there for those data sources/destinations that use them already.
This is useful to deprecate the URL data source and HipChat alert destinations.