Support for resource tracing info #287
Merged
Conversation
This file contains 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
SteveL-MSFT
requested changes
Dec 1, 2023
anmenaga
force-pushed
the
resource_debug_msgs
branch
from
6dc23d5
to
9eddd7f
Compare
SteveL-MSFT
approved these changes
Mar 7, 2024
|
Updated PR Summary to be accurate to latest changes. |
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.
PR Summary
Fix #89
This is a basic support for resources and resource providers to push their diagnostic info to the log of
dsc.exe.Contract is:
If a resource/provider wants to submit a diagnostic message to the DSC, it has to format the message as JSON string with
"Error"/"Warning"/"Info"/"Debug"/"Trace"field and publish it to the STDERR stream.For example:
{"Trace":"PSPath=c:\PowerShell-7.3.1-win-x64"}Strings in the STDERR that are not a valid JSON are ignored (unless exit code is non-zero);
Note:
Timestamps currently show the time when
dscreceives all output when resource process completes. Timestamps will become accurate (i.e. will show exact time when they are generated by a resource/provider) once #46 is done.Example:
