feat: keep the HTML report local-only (stop dumping it in runbooks) - #25
Merged
Conversation
The HTML report is now written only during local execution (Results/). In Azure Automation it is no longer emitted into the job output stream — dumping the full HTML made the log unreadable — so only the run summary line is printed. Bump to 3.1.2. Refs #24
Update CHANGELOG/RELEASE-NOTES and the Configuration wiki: the HTML report is written only during local execution; Azure Automation runs print the per-site actions and a summary line instead of the report. Refs #24
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
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.
Closes #24
Summary
The HTML report is dumped into the Azure Automation job output stream, making the log unreadable. Delivering it elsewhere (Blob/email) was considered but judged too heavy (#23). This keeps the report local-only.
Changes
Results/SPSCleanVersions-<timestamp>.html.EnableReport: falsestill skips the local report.Testing
Invoke-Pester-> 112 passed, 0 failed (report-output test updated to assert local-only, no stream dump). Behaviour validated conceptually against the live runbook run that produced the unreadable dump.Notes
Builds on #22. No change to the report content or the local file.