Undeploy and Resume return ERR_APP_NOT_DEPLOYED for a function that does not exist

Another thing I noticed while working on the eventing management APIs. If a function does not exist (so assume function name foo1), usually all APIs will return a 404 with ERR_APP_NOT_FOUND_TS which makes total sense.

Interestingly, both the resume and undeploy (but not pause or deploy) return ERR_APP_NOT_DEPLOYED instead, which seems inconsistent to me. Specifically, the error is:

{

 "name": "ERR_APP_NOT_DEPLOYED",

 "code": 12,

 "description": "Function not deployed",

 "attributes": null,

 "runtime_info": {

  "code": 12,

  "info": "Invalid operation. Function: foo1 already in undeployed state."

 }

}

Which I think is misleading since the function does not exist vs. being undeployed.