1) and 2) are hacky but will work. However we should really properly support this by giving the generic S3 provider a property. This would require reparenting some code from aws-s3 to s3. Would you be able to submit a PR for this?
The unsigned payload is also a desired feature and easy to add after fixing the above. We plan to release 2.3.0 later this month so it could include these features if you can help out! On Thu, Dec 10, 2020 at 07:42:22PM -0000, John Calcote wrote: > I see someone asked this very question a while back (2018): > https://lists.apache.org/thread.html/3553946dcbe7c72fc8f82c6353c9a5c56d7b587da18a4ebe12df1e26%40%3Cuser.jclouds.apache.org%3E > > Did anyone ever solve the double read issue regarding disabling data-hashing? > > On 2020/12/10 18:03:13, John Calcote <john.calc...@gmail.com> wrote: > > Hi all - > > > > We have a client who would like to use jclouds with ONTAP 9.8, which > > requires V4 signatures AND path-based URL naming. I believe the true AWS S3 > > provider requires virtual bucket URL naming. Anyone have any ideas on how > > to either: > > > > 1) coerce jclouds into using the AWS S3 provider with path-based naming or > > 2) coerce jclouds into using the generic S3 provider with V4 signing > > > > Thanks in advance. > > John > > -- Andrew Gaul http://gaul.org/
