-
Notifications
You must be signed in to change notification settings - Fork 23
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
Errors in reading resource files should be more descriptive and user-friendly #13
Comments
/triage accepted |
This issue synced with: https://issues.redhat.com/browse/MIG-1248 |
/remove needs-triage |
/label ? |
@eriknelson: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/remove-triage |
/remove-label needs-triage |
@eriknelson: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
^ done manually |
If there are files under
exportDir
that don't contain valid resource yaml, the user will see a low-level error message that doesn't indicate what the CLI was trying to do or why it failed. For example, one possible error the user might see is:This sort of message does nothing to tell the user that there's a problem in the files found in the export directory.
The text was updated successfully, but these errors were encountered: