Bump github.com/go-logr/logr from 0.4.0 to 1.2.2

[dependabot]

Bumps github.com/go-logr/logr from 0.4.0 to 1.2.2.

Release notes

Sourced from github.com/go-logr/logr's releases.

v1.2.2

Bugfix release

• funcr: Add a new Option MaxLogDepth which controls how many levels of nested fields (e.g. a struct that contains a struct that contains a struct, etc.) it may log. Every time it finds a struct, slice, array, or map the depth is increased by one. When the maximum is reached, the value will be converted to a string indicating that the max depth has been exceeded. If this field is not specified, a default value will be used.

v1.2.1

This is a minor bugfix release.

• logr: Clarify the Error() semantics. 1) Error messages are always printed (they do not follow V()) and the error argument may be nil.
• funcr: When using RenderValuesHook func would save the "cooked" result, so repeated calls to WithValues() would not merge properly.

v1.2.0

This release has several bug fixes and feature improvements.

• logr: define an optional logr.Marshaler interface for types which want to control how they get logged
• funcr: support fmt.Stringer and error interfaces on values which implement them
• funcr: support logging complex{64,128}
• funcr: fix handling of typed nil when logging a struct via reflection
• funcr: add (optional) JSON output formatting mode
• funcr: better handling of Go's json struct tags (all except "string")
• funcr: handle embedded types more like Go's json package
• funcr: misc performance optimizations
• funcr: add support for modifying or remapping key/value pairs via hook functions
• funcr: optionally log the caller function name
• funcr: fix escaping of strings which contain special characters like line breaks or quotation marks
• funcr: support encoding.TextMarshaler for map keys
• funcr: allow customization of the timestamp format
• funcr: improved testing
• link to zerologr at its new location in the go-logr organization
• various documentation and go doc enhancements

v1.2.0-rc1

This release has several bug fixes and feature improvements.

• logr: define an optional logr.Marshaler interface for types which want to control how they get logged
• funcr: support fmt.Stringer and error interfaces on values which implement them
• funcr: support logging complex{64,128}
• funcr: fix handling of typed nil when logging a struct via reflection
• funcr: add (optional) JSON output formatting mode
• funcr: better handling of Go's json struct tags (all except "string")
• funcr: handle embedded types more like Go's json package
• funcr: misc performance optimizations
• funcr: add support for modifying or remapping key/value pairs via hook functions
• funcr: optionally log the caller function name
• funcr: fix escaping of strings which contain special characters like line breaks or quotation marks
• funcr: support encoding.TextMarshaler for map keys
• funcr: improved testing
• link to zerologr at its new location in the go-logr organization
• various documentation and go doc enhancements

... (truncated)

Changelog

Sourced from github.com/go-logr/logr's changelog.

CHANGELOG

v1.0.0-rc1

This is the first logged release. Major changes (including breaking changes) have occurred since earlier tags.

Commits

• 99e02a9 Merge pull request #124 from thockin/master
• 2ccfbf6 Fix some internal names
• dcef86d funcr: Prevent stack overflow on recursive structs
• dd8f76f Merge pull request #122 from thockin/master
• ebe3534 funcr: fix example verbosity
• de1ec28 Merge pull request #119 from pohly/error-verbosity
• eeeb624 Merge pull request #121 from thockin/master
• f8fce6a docs: clarify Error semantic
• 2750c5e funcr: Fix bug in repeated calls to WithValues
• 8d00e35 Merge pull request #115 from thockin/master
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[Zerpet]

We can't merge this change yet because the controller-runtime 0.10.3 dependency does not support logr 1.2.0 yet. I tried to bump controller-runtime to 0.11.0-beta.0, where they have bumped logr, and it worked with a minor one line change in the scale down controller.

Check these for more context: kubernetes-sigs/controller-runtime#1593 and kubernetes-sigs/controller-runtime#1607

tl;dr: we have to wait for the next version of controller runtime

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.