1 Commits (dependabot/go_modules/main/k8s-io-24cde91f38)

Author	SHA1	Message	Date
Aaron Mark	9a3c040369	fix(template): regression - route registry messages to stderr in template and show (#32217) ... * fix: route registry messages to stderr in template and show When pulling an OCI chart, the registry client prints "Pulled: ..." and "Digest: ..." status lines (and deprecation/underscore warnings) to its configured output writer. Since v4.2.1 (introduced by #32056), these messages leaked into the stdout output of helm template and helm show, breaking downstream consumers such as cdk8s and other YAML parsers. Fix by passing the command's stderr to the registry client in the template and show commands instead of stdout. This keeps stdout clean for machine-readable YAML while still surfacing registry warnings and status messages on stderr for troubleshooting, rather than discarding them. The pull/push commands continue to print these messages on their normal output writer. The show command's addRegistryClient writer parameter is renamed to registryOut and wired through to the registry client, so it is no longer a no-op. Fixes #32215 Signed-off-by: amarkdotdev <amarkdotdev@users.noreply.github.com> * test(cmd): cover registry client stderr routing via OCI pull Exercise helm template and helm show against an in-process OCI registry (repotest.NewOCIServer) and assert Pulled:/Digest: status lines appear on stderr only, keeping stdout free of registry noise. Signed-off-by: amarkdotdev <amarkdotdev@users.noreply.github.com> * test(cmd): drop weak addRegistryClient unit test OCI pull coverage already asserts Pulled/Digest land on stderr, not stdout. Signed-off-by: amarkdotdev <amarkdotdev@users.noreply.github.com> --------- Signed-off-by: amarkdotdev <amarkdotdev@users.noreply.github.com> Co-authored-by: amarkdotdev <amarkdotdev@users.noreply.github.com>	1 month ago