Updates logr, zapr, packet logr, bmclib dependencies #113
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
logr, zapr, packetlogr, bmclib dependencies updated
github.com/go-logr/logr v0.4.0 -> v1.2.2
github.com/go-logr/zapr v0.4.0 -> v1.2.2
github.com/bmc-toolbox/bmclib v0.4.14 -> v0.4.16
packethost/pkg/log/logr -> packethost/pkg/log/logr/v2
bmclib updated in this change because of the indirect (bmclib v0.4.14) dependency on the on logr v0.4.0.
note:
expects linked PR merged packethost/pkg#51 and tagged with
log/logr/v2.0.0
once the linked PR is approved, merged and tagged, go.mod is to be updated to remove the
replace
directive2a4ece9#diff-33ef32bf6c23acb95f5902d7097b7a1d5128ca061167ec0716715b0b9eeaa5f6R44
Why is this needed
The current logr, zapr, packethost/pkg/logr depend on the older 'beta'
logr
package,this change updates the logging dependencies to the current latest.
for more information see packethost/pkg#51
How are existing users impacted? What migration steps/scripts do we need?
No impact on existing users identified