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
[dev.icinga.com #9080] Add commands (actions) for the API #2910
Comments
Updated by mfriedrich on 2015-04-17 15:56:24 +00:00
|
Updated by mfriedrich on 2015-04-17 15:57:18 +00:00
|
Updated by mfriedrich on 2015-04-29 16:18:33 +00:00
|
Updated by mfriedrich on 2015-04-29 16:21:49 +00:00
|
Updated by mfriedrich on 2015-05-19 08:20:37 +00:00
|
Updated by mfriedrich on 2015-06-30 15:09:49 +00:00
|
Updated by mfriedrich on 2015-07-30 17:04:13 +00:00
|
Updated by jflach on 2015-08-04 10:26:21 +00:00 Planed actions:
TODO:
|
Updated by jflach on 2015-08-05 15:42:32 +00:00 TODOS:
|
Updated by mfriedrich on 2015-10-17 01:41:28 +00:00 The naming for global actions is still not good. "notification delivery" sounds as wrong as "performance_data_collection". Probably we should still use "enable-global-notifications" and allow to set the parameter "enable" to whether "true" or "false" and just process that value internally. Users commonly see that "enable_*" attribute all over the other Icinga objects too (e.g. "enable_active_checks" or "enable_perfdata"). |
Updated by mfriedrich on 2015-10-17 16:44:13 +00:00 Another idea - why not entirely drop the global actions? We've recently removed global constants and added them as object attributes to the Icingaapplicakion object. In order to modify these object attributes, one could just POST an update to /v1/objects/icingaapplications/app ... imho that's the more logical way given that all other objects are updated in the same way. This should be mentioned in the documentation of course, and will certainly help removing that complex table still existing - we should add chapters for specific action types anyways before closing this issue too. |
Updated by mfriedrich on 2015-10-22 08:14:07 +00:00
|
Updated by mfriedrich on 2015-10-22 09:29:31 +00:00 Documentation Review:
|
Updated by mfriedrich on 2015-10-22 09:37:22 +00:00
|
Updated by jflach on 2015-10-26 15:00:09 +00:00
I know the downtimes comments are being redone to ConfigObjects, but I have no insight in development process. I will change it in code and documentation once the change is definite. I attached a patch with my changes. Edit: nvm that, I broke the tables |
Updated by jflach on 2015-10-26 16:06:24 +00:00 Changes have been pushed.
|
Updated by mfriedrich on 2015-10-27 17:42:22 +00:00 I've reviewed the latest doc updates and added my changes. Will close this ticket, the other documentation stuff needs to be done with the global doc issue. |
Updated by mfriedrich on 2015-10-27 17:44:27 +00:00
Applied in changeset 1223007. |
Updated by mfriedrich on 2015-11-12 15:34:37 +00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/9080
Created by gbeutner on 2015-04-17 12:27:09 +00:00
Assignee: jflach
Status: Resolved (closed on 2015-10-27 17:44:27 +00:00)
Target Version: 2.4.0
Last Update: 2015-11-12 15:34:37 +00:00 (in Redmine)
Attachments
Changesets
2015-07-30 15:50:17 +00:00 by jflach 9b6ebbc
2015-07-31 15:18:49 +00:00 by jflach 60f86d0
2015-08-20 09:21:56 +00:00 by jflach ccb386e
2015-08-20 12:45:36 +00:00 by jflach ad01b82
2015-08-21 10:48:32 +00:00 by jflach afd6af3
2015-08-21 10:48:32 +00:00 by jflach c5fe46a
2015-08-21 10:49:51 +00:00 by mfriedrich 981ed59
2015-08-24 06:01:33 +00:00 by (unknown) 380b127
2015-08-25 13:14:10 +00:00 by jflach 49682ca
2015-08-26 11:53:17 +00:00 by jflach 01ced15
2015-10-22 09:33:26 +00:00 by jflach be320b2
2015-10-26 16:03:23 +00:00 by jflach 0efab37
2015-10-27 13:15:07 +00:00 by jflach 2fc042e
2015-10-27 17:42:32 +00:00 by mfriedrich 1223007
2015-11-01 15:33:43 +00:00 by mfriedrich 439dad5
Subtasks:
Relations:
The text was updated successfully, but these errors were encountered: