DSC Set does not error when return is not defined and resource returns stdout
Open
Nobody has claimed this yet.
Issue-Bug
- Dominant language
- Rust
- Stars
- 523
- Forks
- 75
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 24
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest version
- Search the existing issues.
Summary
DSC Set method does not throw an error is a resource returns JSON data like in a state or stateAndDiff while the return is not set in the manifest.
Steps to reproduce
Create a DSC resource that returns stdout data while the manifest for Set method does not have return defined
Expected behavior
Error is thrown
Actual behavior
No error is thrown
Error details
Environment data
7.6-preview4
Version
3.2-preview2
Visuals
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with a DSC resource whose Set method returns stdout while the manifest omits return, using PowerShell 7.6-preview4 and DSC 3.2-preview2. Trace the Set result handling and verify that an error is raised for this mismatch, with coverage for the reported behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100