Support `--what-if` for built-in resources
Open
Nobody has claimed this yet.
Issue-Enhancement
Needs Triage
- Dominant language
- Rust
- Stars
- 523
- Forks
- 75
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 24
Description
Summary of the new feature / enhancement
As a user,
I want to be able to call--what-ifon built-in resources,
So I can preview the changes it is going to apply.
Proposed technical implementation details (optional)
With DSC v3.2 shipped, a couple of new built-in resources are introduced with get, set, and export. But these built-in resources are perfect candidates to implement/showcase --what-if:
-
Microsoft.Windows/FirewallRuleList -
Microsoft.Windows/Service -
Microsoft.Windows/FeatureOnDemandList -
Microsoft.Windows/OptionalFeatureList -
Microsoft.Windows/UpdateList -
Microsoft.OpenSSH.SSHD/sshd_config -
Microsoft.OpenSSH.SSHD/Subsystem -
Microsoft.OpenSSH.SSHD/SubsystemList -
Microsoft.OpenSSH.SSHD/Windows
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
Start by tracing the built-in resources named in the checklist, especially FeatureOnDemandList and OptionalFeatureList, alongside their get, set, and export operations. Compare how --what-if is handled for the checked resources, then verify that each listed resource can preview its pending changes without applying them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100