Refactor #1486
The 'status' handler needs to be refactored to use Indirected REST
| Status: | Duplicate | Start date: | 08/02/2008 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | % Done: | 0% |
||
| Category: | plumbing | |||
| Target version: | 2.6.0 | |||
| Affected Puppet version: | 0.24.7 | Branch: | ||
| Keywords: | ||||
| Votes: | 0 |
Description
There is a ridiculously simple ‘status’ handler on XMLRPC right now. We need a similar handler for retrieving status information from our daemons, but it needs to be independent of XMLRPC.
Instead, it should use the Indirector, and it should be able to communicate over REST.
Ideally, we’d provide lots of useful statistical information via this handler, but I don’t know exactly how we’d do that. I’d recommend that the handler return an encoded hash to start, even if the hash is empty (or maybe it could just be something like ‘{:is_on_fire => false}’).
Related issues
History
Updated by Luke Kanies over 3 years ago
- Target version changed from 0.25.0 to 2.6.0
- Affected Puppet version set to 0.24.7
Bump.
Updated by Jesse Wolfe about 2 years ago
- Status changed from Accepted to Duplicate
Duplicated at #3115 due to redmine mishaps.