You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
To fully release logger and structured logging as the default, we need to swap Zarf's default logging from message to logger.
Describe the behavior you'd like
This is a breaking change, so we should also provide a feature flag to reenable message. When using this flag, we should provide a deprecated warning as well as a clear timeline when the old logging will be removed (likely two releases).
Describe alternatives you've considered
We considered deleting all of message but once we found a good path to feature flagging, backwards compatibility is much healthier for our userbase.
We should expect some concerns and feedback to occur only after we've flipped the switch on release. Let's make sure we have time and extra awareness on feedback channels so we can discuss workarounds and followup improvements.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
To fully release logger and structured logging as the default, we need to swap Zarf's default logging from message to logger.
Describe the behavior you'd like
This is a breaking change, so we should also provide a feature flag to reenable message. When using this flag, we should provide a deprecated warning as well as a clear timeline when the old logging will be removed (likely two releases).
Describe alternatives you've considered
We considered deleting all of
message
but once we found a good path to feature flagging, backwards compatibility is much healthier for our userbase.Additional context
Blocked by everything in #3210
Pain Points
We should expect some concerns and feedback to occur only after we've flipped the switch on release. Let's make sure we have time and extra awareness on feedback channels so we can discuss workarounds and followup improvements.
The text was updated successfully, but these errors were encountered: