Class-based resources with Export does not show capability
Open
Nobody has claimed this yet.
Issue-Bug
Need-Review
- 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
The PowerShell adapters should inspect class-based resources AST for a static Export() method and set the capability automatically.
Steps to reproduce
- Create a class-based resource with
Export()method. - Run
dsc resource list --adapter Microsoft.Dsc/PowerShell
Expected behavior
Export cap is listed
Actual behavior
Export cap is NOT listed
Error details
Environment data
7.6-preview6
Version
3.1-preview6
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
Start by tracing the PowerShell adapter used by dsc resource list --adapter Microsoft.Dsc/PowerShell, then inspect how class-based resource ASTs are checked for capabilities. Reproduce the case with a class-based resource containing a static Export() method; done means the command lists the Export capability automatically.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100