Repository navigation
Support plain output messages in Azure Automation - #26
Merged
Merged
Conversation
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.
Azure Automation captures Output messages, while Verbose needs job-wide logging and Information is unsupported.
Write-Color -OutputStream Outputnow emits one joined plain string per call on the success stream. Host remains the default; timestamps, file logging, and-NoConsoleOutputretain their existing behavior.This supports O365Synchronizer issue #52 and O365Synchronizer PR #55. PSWriteColor owns message rendering and stream selection; O365Synchronizer uses a private adapter to keep output logs out of internal contact data. Publish PSWriteColor 1.0.6 before merging the consumer PR and validating its public-package integration.
Validated the full module suite on Windows PowerShell 5.1 and PowerShell 7: 46 tests per runtime. The independent local review found no actionable defects in either candidate. Regenerated command help through PowerForge. Azure Automation job execution is not yet verified.