Feature request: Allow port to be specified for S3
Bug #1475890 reported by
abeverley
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Would it please be possible to allow the port to be specified for the S3 backend? It's a very simple change - see attached patch.
Thanks,
Andy
Changed in duplicity: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
well done!
does that patch work flawlessly with a port not given?
what does boto API expect in that case?
A. the port parameter ommitted?
B. the value set to None?
remember they might change their internal API, so if they do not explicitely give you a 'not set' value, you will have to stick with A.vand then you will have to handle each case with a condition.
..ede/duply.net