fix: remove redundant harbor logLevel

[j-zimnowoda]

No description provided.

[martijncalker]

Why not make this configurable?

And thinking about this even more, why not make log_level global configuration in order to run every service in debug mode?

[j-zimnowoda]

Making global debug would make a noise and put a lot of pressure on the platform.
So far we did not expose any log level to the values.
Anyway it is worth to consider doing it. @Morriz what do you think ?

[j-zimnowoda]

@martijncalker please define a task for that, as exposing debug flag should be done for all services in a consistent way.

[Morriz]

does this have a corresponding issue @j-zimnowoda ? Please link

[Morriz]

I am against one-for-all debug flag. Use debug levels surgically in one solution only when devving or troubleshooting. I am actually against putting them in the values, but it helps to find them there. The danger is that we don’t put it back to normal

…

On 4 Nov 2020, at 13:56, jeho ***@***.***> wrote:  @j-zimnowoda commented on this pull request. In values/harbor/harbor.gotmpl: > @@ -6,7 +6,8 @@ {{- $harborSecretName := ($harborDomain | replace "." "-") }} {{- $notarySecretName := ($notaryDomain | replace "." "-") }} {{- $externalUrl := printf "https://%s" $harborDomain }} -logLevel: debug + # logLevel - debug, info, warning, error or fatal +logLevel: info @martijncalker please define a task for that, as exposing debug flag should be done for all services in a consistent way. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.