Martijn van Groningen ba17333523 get watch api: Return the watch status separate from the watch source. ... The status isn't maintained by the user but rather by Watcher itself. The idea here is that the get watch api should return the watch as was provided to Watcher via the put watch api. The status will be reported under the top level `_status` field. Original commit: elastic/x-pack-elasticsearch@54e2452493		2015-06-24 21:31:52 +02:00
..
ack_watch	[TEST] Watch action acking and throttling tests	2015-06-06 02:35:42 +02:00
delete_watch	[REST-TEST] Add master_timeout to the rest API specs	2015-05-07 19:19:49 -04:00
execute_watch	Renamed `email.email` to `email.message` in the email action result.	2015-06-18 11:20:55 +02:00
get_watch	get watch api: Return the watch status separate from the watch source.	2015-06-24 21:31:52 +02:00
hijack	Hijack the DELETE .watches index delete endpoint.	2015-05-08 10:39:06 -04:00
put_watch	Require units for all time values	2015-06-22 11:47:37 +02:00
restart_watcher	Change watcher REST API call namespace to be watcher.	2015-04-28 18:50:07 -04:00
start_watcher	Change watcher REST API call namespace to be watcher.	2015-04-28 18:50:07 -04:00
stats	Refactored `WatcherService.State`	2015-05-06 12:29:59 +02:00
stop_watcher	Change watcher REST API call namespace to be watcher.	2015-04-28 18:50:07 -04:00
watch_info	[REST-TEST] Remove check for snapshot.	2015-05-20 09:58:05 -04:00