Abstract operational actions? (start/stop/install/remove/etc

[jordansissel]

A chat with @coderanger on IRC about implementing a pleaserun chef resource type, he gave a convincing argument for why pleaserun's abstraction should be extended to include operational actions like start and stop.

Sounds good to me! Let's figure out what that would look like.

[igalic]

What was that convincing argument?

[jordansissel]

(summarizing the conversation I had with @coderanger about this)

I suppose it was two parts. First, the small claim that Chef doesn't handle different service types very well. Puppet may have the lead here, but Chef has 'service' and 'runit_service' and 'supervisor_service' and such instead of one unifying resource type with multiple providers (intentionally? accidentally? It doesn't matter). Second, that since pleaserun already has this notion of actions (install_actions), it's not a stretch to try generalizing that idea to other kinds of actions (start, stop, and remove actions).