helm/pkg/cmd/testdata
Benoit Tigeot 6b5fa33633
debug log level is dynamic and set after Logger creation
So we should use dynamic handler to set the log level after. With this
patch we can clearly see the output. Before we were always stuck in log
level "info" and not seeing debug log level

```
bin/helm upgrade --install --debug --wait frontend \
--namespace test \
--set replicaCount=2 \
--set backend=http://backend-podinfo:9898/echo \
podinfo/podinfo
level=DEBUG msg="getting history for release" release=frontend
level=DEBUG msg="preparing upgrade" name=frontend
level=DEBUG msg="performing update" name=frontend
level=DEBUG msg="creating upgraded release" name=frontend
level=DEBUG msg="checking resources for changes" resources=2
level=DEBUG msg="no changes detected" kind=Service name=frontend-podinfo
level=DEBUG msg="patching resource" kind=Deployment name=frontend-podinfo namespace=test
level=DEBUG msg="waiting for resources" count=2 timeout=5m0s
level=DEBUG msg="waiting for resource" name=frontend-podinfo kind=Deployment expectedStatus=Current actualStatus=Unknown
level=DEBUG msg="updating status for upgraded release" name=frontend
Release "frontend" has been upgraded. Happy Helming!
NAME: frontend
LAST DEPLOYED: Thu Apr 10 09:56:25 2025
NAMESPACE: test
STATUS: deployed
REVISION: 6
DESCRIPTION: Upgrade complete
```

Signed-off-by: Benoit Tigeot <benoit.tigeot@lifen.fr>
2025-04-10 10:03:13 +02:00
..
helm home with space/helm squash 2025-02-24 15:11:54 +00:00
helmhome/helm squash 2025-02-24 15:11:54 +00:00
output squash 2025-02-24 15:11:54 +00:00
testcharts debug log level is dynamic and set after Logger creation 2025-04-10 10:03:13 +02:00
testplugin squash 2025-02-24 15:11:54 +00:00
testserver squash 2025-02-24 15:11:54 +00:00
helm-test-key.pub squash 2025-02-24 15:11:54 +00:00
helm-test-key.secret squash 2025-02-24 15:11:54 +00:00
password squash 2025-02-24 15:11:54 +00:00
plugins.yaml squash 2025-02-24 15:11:54 +00:00
repositories.yaml squash 2025-02-24 15:11:54 +00:00