Closed colinodell closed 1 month ago
This issue is currently awaiting triage.
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.
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:https://github.com/kubernetes-sigs/kustomize/blob/e244b83844cd5e1d114b731713c7f437e510c023/api/internal/target/kusttarget.go#L451-L457
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