-
Notifications
You must be signed in to change notification settings - Fork 25
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
"Hooks" Concept #55
Comments
I love the idea, and since NSoT is built around Django which already has an underlying event hook system, we'd really have to capitalize on that on the server side. And THEN we could implement that on the client side to make it easily usable. |
I wonder what the best way to 'upload' hooks from the client would be. |
Hooks functionality is now only blocked on unittests. Please refer to the PR and NSoT Issue We should work on getting this implemented from the client-side. Should be pretty easy. EventsEvents are defined in the This is in the format of
Creating a hookPayload: {
"event": "see list",
"target": "http://url/to/post",
"global_hook": true
}
Updating a hookPayload: {
"event": "see list",
"target": "http://url/to/post",
"global_hook": false
}
Deleting a hook
Args
|
How rad would it be to have a hooks concept? I would like to maybe think about it in the next couple days to see if I could help add this functionality.
What 'design' would fit best into the nsot world? Something that allows you to set up hooks to get notified about each resource modification, creation, and deletion. Really as long as the resource object can be passed, each hook could take it from there at the basic level. At a more specific level it could be worked so you create a network-hook or a site-hook, but not sure if there'd be much extra value there.
Thoughts?
The text was updated successfully, but these errors were encountered: