Comment 2 for bug 1334283

"Fixing" this would be a behavior change unfortunately. I'm not sure we can do that without offering the older, less strict behavior. There are likely template authors relying on it. Consider a scenario where all possible configuration for a particular application is kept in a file, but deployments that don't set anything are used quite often.

So unless people decide that breaking existing templates is o-k, we'll likely have to introduce some kind of "strict_input_values: true" property for the deployment.