Have metadata that informs, on average, how long a configuration is expected to run
Open
Nobody has claimed this yet.
Issue-Enhancement
Partner-WinGet
- Dominant language
- Rust
- Stars
- 523
- Forks
- 75
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 24
Description
Summary of the new feature / enhancement
DSCv3 currently already emits how long a configuration takes to run, it would be interesting to allow configuration authors to supply this in the metadata section like expectedRuntime to give an idea if it takes minutes, hours, days, etc... which would be presented as progress.
Also allow the same metadata per resource execution.
Proposed technical implementation details (optional)
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
The issue names no files, tests, or entry points. Start by tracing the existing configuration runtime reporting and progress presentation, then identify how configuration and resource metadata are parsed; done means both configuration-level and per-resource expected runtimes are represented and shown consistently.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100