Define behavior in failure scenarios with nested packages #1084
Labels
area/live
area/pkg
design-doc
enhancement
New feature or request
p1
size/M
2 day
triaged
Issue has been triaged by adding an `area/` label
The current behavior is that we mostly continue in the face of errors. For example, if I want to create a setter, but an existing setter with the same name already exists in one of the subpackages, we will just print an error for that package and keep going. We should have a clear and consistent vision for how we should handle these situations across all the commands in kpt.
The text was updated successfully, but these errors were encountered: