-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
ResolutionRequest
error getting resource is kind of ugly
#5409
Comments
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
Rotten issues close after 30d of inactivity. /close Send feedback to tektoncd/plumbing. |
@tekton-robot: Closing this issue. 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. |
Prompted by #5405 (comment)
The error that gets returned to the
ResolutionRequest
reconciler when the relevant resolver hits an error fetching the resource is a bit ugly:This is coming from https://github.com/tektoncd/pipeline/blob/5188483f1d2d9fb34d0df910c1e84be30676f941/pkg/resolution/common/errors.go#L103-L102. We should check whether this error message ever actually gets surfaced to users, and if so, we should probably make it more useful/clear.
/kind misc
The text was updated successfully, but these errors were encountered: