Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define behavior in failure scenarios with nested packages #1084

Closed
mortent opened this issue Sep 29, 2020 · 0 comments
Closed

Define behavior in failure scenarios with nested packages #1084

mortent opened this issue Sep 29, 2020 · 0 comments
Assignees
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

Comments

@mortent
Copy link
Contributor

mortent commented Sep 29, 2020

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.

@mortent mortent added area/cfg area/live area/pkg enhancement New feature or request p1 triaged Issue has been triaged by adding an `area/` label labels Sep 29, 2020
@mortent mortent self-assigned this Sep 30, 2020
@mikebz mikebz added the size/M 2 day label Oct 28, 2020
@mortent mortent closed this as completed Jan 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

No branches or pull requests

2 participants