Closed ialidzhikov closed 2 months ago
I hope that we can tackle this in one go, once we refactored all gardener components to zap/logr (part of https://github.com/gardener/gardener/issues/4251). Then we can probably introduce some common flags, that will be used in all gardener components and extensions alike. Also, ref https://github.com/gardener/gardener/issues/4803#issuecomment-783517394
/help
@Kostov6 Here my list of commands:
/remove-lifecycle rotten /good-first-issue
@Kostov6 Command /remove-lifecycle
is not known.
@Kostov6 Command /good-first-issue
is not known.
$ docker run europe-docker.pkg.dev/gardener-project/releases/gardener/extensions/provider-aws:v1.57.0 --help | grep log
--log-format string The format for the logs. Must be one of [json,text] (default "json")
--log-level string The level/severity for the logs. Must be one of [info,debug,error] (default "info")
It seems it comes from https://github.com/gardener/gardener/pull/6875 We can close this issue
/close
How to categorize this issue?
/area ops-productivity usability /kind bug /priority 3 /platform aws
What happened: I don't see an option/flag how I can configure the log level in the extension:
For example the terraformer package logs with
.V(1)
in several places - for more details see https://github.com/gardener/gardener/issues/4978. Currently there is no way to enable this logging.What you expected to happen: To have an option/flag about the log level.
How to reproduce it (as minimally and precisely as possible): See above.
Anything else we need to know?: This issue is not only applicable to provider-aws but I think it is applicable also for all of other provider extensions (at least the ones under github.com/gardener).
Environment:
kubectl version
):