Enable passing top-level `name` property as metadata to resources
Open
Nobody has claimed this yet.
Issue-Enhancement
Partner-MC
- Dominant language
- Rust
- Stars
- 523
- Forks
- 75
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 24
Description
Summary of the new feature / enhancement
Resources may need to process the user-defined name top-level property but resources only receive the object under properties. There is already a provision to pass additional context via _metadata to a resource, so this can be passed as _name (since that property is how resources inform DSC to populate the name top-level).
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
Start by tracing the existing resource handling for the _metadata context and the top-level name property. Confirm where resource input is assembled, then add the _name context and verify that resources can receive it while existing metadata behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100