You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The web server uses a catch-all authentication challenge web page
The resource is successfully retrieved as a base but directory accumulation fails for any reason
... the error from the third step is not reported.
The first two conditions are identical to #5540, so I'll quote the relevant bits here:
Since a catch-all authentication challenge web page is in place, the attempt to accumulate the resource as a file receives a 200 response. As a result, fileloader.httpClientGetContent() does not do a check of the path to see if it's a git repo. That means FromFile processes the HTML of the web page, and properly returns a YAML parse error.
accumulateResources then attempts to process the resource as a git reference.
Unlike #5540, the remote repository is successfully cloned, so the code proceeds to call kt.accumulateDirectory(). If that accumulation fails for any reason, a decision is made how to report the failure. But if errF (from earlier in the method) was a malformed YAML error, the error from kt.accumulateDirectory() is dropped:
SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.
The triage/accepted label can be added by org members by writing /triage accepted in a comment.
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-sigs/prow repository.
What happened?
Under these conditions ...
... the error from the third step is not reported.
The first two conditions are identical to #5540, so I'll quote the relevant bits here:
Unlike #5540, the remote repository is successfully cloned, so the code proceeds to call
kt.accumulateDirectory()
. If that accumulation fails for any reason, a decision is made how to report the failure. But iferrF
(from earlier in the method) was a malformed YAML error, the error fromkt.accumulateDirectory()
is dropped:kustomize/api/internal/target/kusttarget.go
Lines 451 to 457 in e244b83
The result is that the user does not receive any information about why kustomize failed to accumulate the directory. They instead see an error like:
What did you expect to happen?
I expect to see the error from accumulating the directory - something like:
How can we reproduce it (as minimally and precisely as possible)?
I unfortunately don't have a fully working reproducer I can share :-/
Expected output
No response
Actual output
No response
Kustomize version
v5.4.1
Operating system
None
The text was updated successfully, but these errors were encountered: