Add pass-through output format for dsc resource get
#862
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
tgauth
approved these changes
Jun 5, 2025
SteveL-MSFT
force-pushed
the
resource-pass-through
branch
from
7c343fb to
c678d8e
Compare
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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
Add
pass-throughoutput format fordsc resource getwhich emits the JSON from the resource without adding a wrapperFixed some cases where the error text wasn't using i18n or remove the unnecessary
Error:prefix to the message sinceerror!()macro already emits that.Note that only
gethas this capability sincesetandtesthave variable output from resources and the value is wrapped by DSC for before/after or desired/actual.exportalready has equivalent viaget --all(if I knew this was coming, I would have had it done this way forexport, but oh well)PR Context
cc @Bpoe