Write log lines in the shared session log format and fix the -v flag - #19
Merged
Conversation
Log-file lines are now "[yyyy-MM-dd HH:mm:ss] LEVEL message" in local time, with the level left-aligned in a five-character column and limited to DEBUG, INFO, WARN and ERROR. Section, progress, success and skipped markers are written as INFO lines that carry the marker in the message; the console output keeps its icons and is unchanged. The 30-day retention sweep at logger initialisation is already in place and is unchanged; the README now documents it alongside the line format. "-v" was matched as the version switch before it could be read as verbose, so "managedbootstrapinstall.exe -v" printed the version and exited. "-v" and "--verbose" now both mean verbose; "--version" and "-V" print the version.
rodchristiansen
marked this pull request as ready for review
September 1, 2026 23:53
rodchristiansen
added a commit
that referenced
this pull request
Sep 2, 2026
…19) Log-file lines are now "[yyyy-MM-dd HH:mm:ss] LEVEL message" in local time, with the level left-aligned in a five-character column and limited to DEBUG, INFO, WARN and ERROR. Section, progress, success and skipped markers are written as INFO lines that carry the marker in the message; the console output keeps its icons and is unchanged. The 30-day retention sweep at logger initialisation is already in place and is unchanged; the README now documents it alongside the line format. "-v" was matched as the version switch before it could be read as verbose, so "managedbootstrapinstall.exe -v" printed the version and exited. "-v" and "--verbose" now both mean verbose; "--version" and "-V" print the version.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
[yyyy-MM-dd HH:mm:ss] LEVEL messagein local time, with the level left-aligned in a five-character column and limited toDEBUG,INFO,WARNandERROR. Section, progress, success and skipped markers are written asINFOlines that carry the marker text in the message. Console output keeps its icons and is unchanged.-vwas matched as the version switch before it could be read as verbose, somanagedbootstrapinstall.exe -vprinted the version and exited.-vand--verbosenow both mean verbose;--versionand-Vprint the version. Help text and README updated.Logger.Initializeis already in place and is unchanged; the README now documents it alongside the line format.Verification
dotnet build BootstrapMate.csproj -p:EnableWindowsTargeting=truesucceeds (only the two pre-existing warnings).Logger.csin a throwaway harness against a temp directory: every emitted line matches^\[\d{4}-\d{2}-\d{2} \d{2}:\d{2}:\d{2}\] (DEBUG|INFO |WARN |ERROR), a 31-day-old.logis deleted, a 29-day-old one is kept, and non-.logfiles are untouched.