-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
*: remove v1/alerts/groups API endpoint #1525
*: remove v1/alerts/groups API endpoint #1525
Conversation
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.
Looks good to me. Thanks for the thorough cleanup. Just to ensure, that we are mentioning this in the release notes, would you please add an entry to the Next release
section of CHANGELOG.md
in this PR?
@@ -71,6 +71,15 @@ var corsHeaders = map[string]string{ | |||
"Cache-Control": "no-cache, no-store, must-revalidate", | |||
} | |||
|
|||
// Alert is the API representation of an alert, which is a regular alert | |||
// annotated with silencing and inhibition info. | |||
type Alert struct { |
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.
Great! Thanks for moving APIAlert into api/api.go
.
@mxinden done! |
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.
alertSlice()
on dispatch.go#246 can also be removed, then this is good to go
In case one of you clicks merge first, would you mind squashing? Makes preparing the CHANGELOG.md easier for the next release. |
squash4lyfe |
@simonpasquier would you mind resolving the conflict? |
Signed-off-by: Simon Pasquier <[email protected]>
Signed-off-by: Simon Pasquier <[email protected]>
Signed-off-by: Simon Pasquier <[email protected]>
789fe15
to
a7738d2
Compare
@mxinden done |
Thanks @simonpasquier! |
Hi @simonpasquier @mxinden, sounds like removing the "v1/alerts/groups" endpoint from the V1 API has broken compatibility with some external clients.. e.g. I wonder if it make sense to just put api/v1/alerts/groups back in? (E.g. just re-add the code that was removed from this PR?) As:
|
Yes +1 for adding it back. We use karma. |
Yes, understood. It looks like #868 is now updated to "P2", so hopefully that update/fix gets added soon(ish). Just keep in mind that there will be users out there that are not able to update unsee/karma or alertmanager until this endpoint gets returned or replaced. Thx @simonpasquier |
Closes #1508
I had this change for a while in my backlog, just rebased on master to fix some conflicts.