feat: add ability to specify signature type on s3 cache
What does this MR do?
This MR adds ability to specify which signature type needs to be used to connect and generate presigned urls targeting an s3 server
Why was this MR needed?
I currently use a third party s3 provider which only support s3v2 signature types
Are there points in the code the reviewer needs to double check?
Does this MR meet the acceptance criteria?
-
Documentation created/updated -
Added tests for this feature/bug -
In case of conflicts with master
- branch was rebased
What are the relevant issue numbers?
Edited by Manu Chambon