new feature: Support OCI artifacts
- Dominant language
- Rust
- Stars
- 5.4k
- Forks
- 825
- Avg merge
- 1d 14m
- Merged PRs (30d)
- 127
Description
### Feature Description
I would love to see support in opendal for OCI artifact reading/extraction (see [1])
[1] https://oras.land/docs/quickstart
### Problem and Solution
We have integrated support in jumpstarter for opendal as our storage layer for accessing storage, or passing presigned storage access to edge elements.
https://github.com/jumpstarter-dev/jumpstarter/tree/main/packages/jumpstarter-driver-opendal/jumpstarter_driver_opendal
handling OCI artifacts is becoming standard in the industry to transport device images, or firmware, and we would like to take advantage of that.
CC: @NickCao
### Additional Context
We don't have capacity to work on this at the moment.
### Are you willing to contribute to the development of this feature?
- [ ] Yes, I am willing to contribute to the development of this feature.
Contributor guide
Research direction
Start with the ORAS quickstart linked in the issue, then review OpenDAL's existing storage-layer integration used by jumpstarter_driver_opendal. Define the scope for OCI artifact reading and extraction, identify the relevant OpenDAL entry points and tests, and consider the feature complete when an OCI artifact can be accessed and extracted through OpenDAL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100