Describe the problem/challenge you have
When a user provides configuration to kapp but that configuration contains a typo or a key that should not be part of the configuration, kapp does not error out or tell the user that the configuration has keys that kapp does not know off.
Describe the solution you'd likekapp should return an error saying something like
Error: Configuration have the following unknown fields:
rebaseRules[0].resourcesMatchers
unknownKey
Anything else you would like to add:
For a better UX maybe if it would be easy we should provide the line of the file where this error occurs. We should be mindful that maybe the configuration can be piped into kapp so there will be no filename.
upgradability issue: If keys are introduced in newer version, validation will fail older versions. (using new config with old kapp). Needs to be also seen how it will work with kapp-controller.
Describe the problem/challenge you have When a user provides configuration to
kapp
but that configuration contains a typo or a key that should not be part of the configuration,kapp
does not error out or tell the user that the configuration has keys thatkapp
does not know off.One example would be
the key
resourcesMatchers
does not existDescribe the solution you'd like
kapp
should return an error saying something likeAnything else you would like to add: For a better UX maybe if it would be easy we should provide the line of the file where this error occurs. We should be mindful that maybe the configuration can be piped into
kapp
so there will be no filename.