PowerShell based DSCv3 resources
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 523
- Forks
- 75
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 24
Description
Summary of the new feature / enhancement
Recently it was identified that classes have a by-design limitation of not being supported in Constrained Language Mode (unless signed and trusted). Also, we want to have the PowerShell script called via pwsh -f and not pwsh -c as that ensures proper execution policy is applied. As a script, it would still need to be signed for full language, but some resources may work unsigned in constrained language.
Proposed technical implementation details (optional)
Need to think through how to define a structure in script so that the adapter can parse it appropriately and keep it easy for developers to author. For example, can we leverage comment based help here.
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
The issue does not name files, tests, or an entry point. Start by tracing the DSCv3 adapter's current class-resource execution and its pwsh invocation, then review how resource structure and comment-based help could be parsed. Done means a defined script-resource structure and an agreed execution path using pwsh -f.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100