WIP Remove support for legacy logging #3546
Draft
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
WIP: two major categories of work to finish here:
1: Fully log-format="legacy" while ensuring message is still set up properly to print non-log messages like Yaml and tables.
2: Chase down every message log statement, spinner, and progress bar in the main zarf codebase. This involves a bunch of changes in packager(1) but should be a net-zero change in behavior for any user not running --log-format=legacy.
The plan is: get it compiling, then rip out the CLI layer, then chase down remaining logs and any debug coverage we might have missed the first go around.
TODO: Document and flag all breaking changes.
Related Issue
Fixes #3500
Relates to #2576
Checklist before merging