Introduction of detailed S3 parameters breaks existing AWS setups
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Fix Released
|
High
|
Unassigned | ||
duplicity (Ubuntu) |
Fix Committed
|
Low
|
Unassigned |
Bug Description
Hi,
I just got an update of duplicity via snap to version 0.8.15.
Running my backup script running duplicity as follows:
```
duplicity incremental
--include-filelist backup_
--exclude-filelist backup_
--exclude-
--exclude-
--progress \
--full-
$HOME \
boto3+s3:
```
...resulted in the following error:
```
Traceback (innermost last):
File "/snap/
with_
File "/snap/
fn()
File "/snap/
action = commandline.
File "/snap/
backup, local_pathname = set_backend(
File "/snap/
config.backend = backend.
File "/snap/
obj = get_backend_
File "/snap/
return factory(pu)
File "/snap/
self.
File "/snap/
self.s3 = boto3.resource(
AttributeError: module 'duplicity.config' has no attribute 's3_region_name'
```
*Actual behaviour*
It seems like the changes introduced via https:/
*Expected behaviour*
These parameters should be optional.
*Duplicity version*: 0.8.15
*Python version*: 3.6
*OS distro and version*: Ubuntu 20.04
*Target filesystem*: Linux to AWS S3
Thanks for your work!
EDIT: Added duplicity command.
description: | updated |
Changed in duplicity: | |
importance: | Undecided → High |
milestone: | none → 0.8.16 |
status: | New → Fix Committed |
Changed in duplicity (Ubuntu): | |
importance: | Undecided → Low |
status: | New → Fix Committed |
Changed in duplicity: | |
status: | Fix Committed → Fix Released |