apache
Tracking issues for reqsign-core v2
reqsign underwent a big refactor that splits its crate structure into reqsign-core and service-specific crates such as reqsign-aws-v4. It also released version v2, enabling us to expose the reqsign API directly as part of our public API.
This tracking issue is used to track the migration process to reqsign-core v2. We will migrate all existing uses of reqsign to use reqsign-core and move the credentials implemented by ourselves to reqsign.
Tasks
Migrate to reqsign-core
- [ ] azblob
- [ ] azdls
- [ ] azfile
- [ ] cos
- [ ] gcs
- [ ] obs
- [ ] oss
- [x] #6560
Implemented in reqsign
- [ ] aliyun_drive
- [ ] b2
- [ ] dropbox
- [ ] gdrive
- [ ] huggingface
- [ ] onedrive
- [ ] upyun
I'm working locally on this but reqsign missed some features we need, will wait for another release of reqsign.
Hi @Xuanwo, I’ve been following the reqsign-core v2 migration work and the recent progress around #6560. I’m interested in contributing to this tracking issue and helping migrate one of the remaining services to reqsign-core v2.
I’m planning to start with a single service (for example oss or obs) and submit an incremental PR to establish a clear migration pattern before proceeding further.
Before starting, I wanted to check: Are there any remaining gaps or constraints in reqsign-core v2 that contributors should be aware of? Is there a preferred service to start with, or any ordering you’d recommend?
Happy to align with the current road map and proceed step by step. Thanks!
