rjrudin
commented
1 year ago @ryanjdew I did a quick check to make sure this has no impact on DHF - DHF doesn't have any tasks using the "deploy or undeploy a single command" methods. So no impact on DHF, though if DHF were to use those methods at some point, I think it would still want this behavior - i.e. an error instead of a silent failure when a non-existent command is requested.
This would only happen on a programming error - in which case we almost certainly want an error because the caller is expecting a command to be executed and that's not being done. Ran into this when I was testing out a PR but I had not yet published ml-app-deployer, and a task was silently failing because the command wasn't found. An error is much better in that scenario.