I believe that the discussion did end with the notion that triggers, jobs, and streams would have a lifecycle

Does not exist -> Defined -> Deployed -> Undeployed ->Undefined

As of right now, undeploy and delete (aka undefined) are not part of the ResourceDeployer interface.  StreamDeployer (which ATM doesn't inherit from ResourceDeployer) does have this functionality.

In other words, there is probably some more work that needs to be done in TriggerDeployer (perhaps just by inheritance of new methods added to AbstractDeployer) before the shell command can come into play.

It would probably be a good idea to create a google doc for the shell commands, so that we are all in agreement with the end user exposed lifecycle of taps, streams, etc..

glenn/ilaya - can you take a shot at that doc?  Pull in whoever you need when you have questions.