allow specifying version, signature, hash of resource
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
To ensure a specific version (range?) is used or identify of the resource as well as supporting use of different versions of the same resource, we should leverage metadata property to allow describing resource requirements like version (range), hash, etc...
Proposed technical implementation details (optional)
Similar to the execution context for metadata, we can just have metadata at the resource level:
resources:
- name: version1
type: Test/MyResource
metadata:
Microsoft.DSC:
resourceRequirements:
version: "[1.0.0,2.0.0)" # nuget version range syntax indicating 1.x.x but not including 2.0.0
properties:
a: 1
b: 2
The Microsoft.DSC namespace avoids collisions, but makes it more nested. Adapters would need to opt-in to support this.
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
No files or tests are named. Start by reviewing the existing execution-context metadata handling, then trace how resource-level metadata reaches adapters. Done means defining and implementing resource requirements for version ranges, hashes, or related identifiers, with adapter opt-in as proposed.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100