-
Notifications
You must be signed in to change notification settings - Fork 34
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 DeleteGraphDef to graph-defs API #157
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
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.
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.
Oops, this is the first DELETE API requiring the request body :)
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.
Yes :) We did so, although it is somewhat unusual, because while it is common to DELETE a resource by including an ID or similar in the URL path, I was hesitant to include a part of the metric name in the path as an ID.
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 you could use the percent encoded name in path like
/api/v0/hosts-by-custom-identifier/{custom-identifier}
, but I'm not strongly against using the request body. My another concern is the verb in the paths is unusual in Mackerel APIs. For examplePOST /api/v0/graph-defs
andDELETE /api/v0/graph-defs
(orDELETE /api/v0/graph-defs/{metric-name}
) are more aligned to other APIs? I remember some (Google?) API design guides recommendPOST /{resource-name}/:{verb}
, but consistency in the API set is more important anyway. ThePOST /api/v0/graph-defs/create
is an old(est?) API so you'll need to keep the alias forever (GET /api/v0/hosts.json
is still there I believe).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.
We considered the idea of putting the
name
parameter in the URL path, but we thought it was unnatural as our internal data model (sorry for the internal talk). We are still puzzled, but we decided to put it in the request body. I hope you will forgive me.Regarding the second topic, you are absolutely right about the
/delete
in the URL path. It should beDELETE /api/v0/graph-defs
. We will fix it, so please wait.