duplicity-team team mailing list archive

[Rinck Sonnenberg <r.sonnenberg@xxxxxxxxx>]

Hi all,

for those struggling with the changed S3 behavior in duplicity/boto3
regarding the --s3-endpoint-url, I thought I'd give an example. I took my
some trial and error to figure out what needed to go where.

So if previously (before 0.8.23) you were using a destination like:
duplicity --s3-use-new-style --s3-european-buckets /mypath s3://
s3.eu-west-1.amazonaws.com/my-bucket-name/

the new syntax (0.8.23+) should be something like:
duplicity --s3-use-new-style --s3-european-buckets --s3-endpoint-url
https://s3.eu-west-1.amazonaws.com/ /mypath s3://my-bucket-name/

Hopefully that will save someone some headaches! :-)

Regards,
Rinck



On Thu, Mar 24, 2022 at 4:55 PM Kenneth Loafman via Duplicity-talk <
duplicity-talk@xxxxxxxxxx> wrote:

> We made the following changes and released them in *0.8.23.dev15*
> development version on GitLab, Launchpad PPA, Snapcraft (edge), and PyPi.
> If you use the release/stable version, please use this for planning
> purposes.  *This will be part of 0.8.23 in a month or so.*
>
> Since some users use the dev version, here are the changes:
>
>    - boto3 backend is now default s3:// backend. It does not support
>    s3:/// but needs --s3-endpoint-url instead
>    - boto3 supports --s3-unencrypted-connection option now
>    - boto backend now usable via boto+s3:// or boto+gs:// only
>    - boto's s3+http:// scheme was removed, use boto+s3:// instead
>    - boto supports --s3-endpoint-url. --s3-use-deep-archive options now
>    - changes are documented in man page
>
> I would suggest that if/when this breaks things, please consult the man
> page.  There are a bunch of much needed updates that will see you through.
>
> ...Thanks,
> ...Ken
>
> _______________________________________________
> Duplicity-talk mailing list
> Duplicity-talk@xxxxxxxxxx
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>