This diverges from the current behavior of update, which simply updates the definition of the app for subsequently launched tasks.  This might be what we want, but I suspect not.  Currently, users are required to submit two API requests to get this result: first scale the app to zero instances, and then put the new app definition (including the desired number of instances).  The semantics of this operation are subtle, so I'd like to hear what others think this should do.