#90 S3: TARGET_USER/PASS have no effect

[Jonas Haag]

S3: TARGET_USER and TARGET_PASS are not being passed to boto. You have to export AWS_* and not use TARGET_USER/PASS in your duply config. This is outright confusing; duply should rather export these AWS_* on its own.

[ede]

On 31.12.2015 12:28, Jonas Haag wrote:

---

** [bugs:#90] S3: TARGET_USER/PASS have no effect**

Status: open
Group: duply
Labels: s3
Created: Thu Dec 31, 2015 11:28 AM UTC by Jonas Haag
Last Updated: Thu Dec 31, 2015 11:28 AM UTC
Owner: nobody

S3: TARGET_USER and TARGET_PASS are not being passed to boto. You have to export AWS_* and not use TARGET_USER/PASS in your duply config. This is outright confusing; duply should rather export these AWS_* on its own.

sorry Jonas,

more and more new backends for duplicity start using backend specific env. vars . even older ones like s3 want this or that option set that way.

so unless you are offering timely updated routines for all of them i decided to remove translation of TARGET/USER to these vars completely for all backends not using a simple user/pass scheme.

hope this makes sense to you too.. ede/duply.net

[Jonas Haag]

What do you think of this patch then? You know, because S3 is pretty commonly used :-)

@@ -778,7 +778,7 @@
 # for details and available backends see duplicity manpage, section URL Format
 #   http://duplicity.nongnu.org/duplicity.1.html#sect7
 # NOTE:
-#   some backends (eg. cloudfiles) need additional env vars to be set to
+#   some backends (eg. Cloudfiles, AWS) need additional env vars to be set to
 #   work properly, when in doubt consult the man page mentioned above.
 # ATTENTION:
 #   characters other than A-Za-z0-9.-_.~ in the URL have to be

[ede]

you essentially want me update the help comments in the conf template with more protocols that need to export the params themselves?

let's cut a deal. you check the manpage
http://duplicity.nongnu.org/duplicity.1.html#sect7
sections 'URL Format' and the 'Notes' sections for the backends and deliver examples like already given for cloudfiles. i'll add them commented to the conf template for user convenience.

..ede

On 31.12.2015 14:48, Jonas Haag wrote:

What do you think of this patch then? You know, because S3 is pretty commonly used :-)

~~~~
@@ -778,7 +778,7 @@
# for details and available backends see duplicity manpage, section URL Format
# http://duplicity.nongnu.org/duplicity.1.html#sect7
# NOTE:
-# some backends (eg. cloudfiles) need additional env vars to be set to
+# some backends (eg. Cloudfiles, AWS) need additional env vars to be set to
# work properly, when in doubt consult the man page mentioned above.
# ATTENTION:
# characters other than A-Za-z0-9.-_.~ in the URL have to be
~~~~

---

** [bugs:#90] S3: TARGET_USER/PASS have no effect**

Status: open
Group: duply
Labels: s3
Created: Thu Dec 31, 2015 11:28 AM UTC by Jonas Haag
Last Updated: Thu Dec 31, 2015 11:28 AM UTC
Owner: nobody

S3: TARGET_USER and TARGET_PASS are not being passed to boto. You have to export AWS_* and not use TARGET_USER/PASS in your duply config. This is outright confusing; duply should rather export these AWS_* on its own.

---

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/ftplicity/bugs/90/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

[Jonas Haag]

S3: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY
Azure: AZURE_ACCOUNT_NAME, AZURE_ACCOUNT_KEY
Cloudfiles: CLOUDFILES_USERNAME, CLOUDFILES_APIKEY, CLOUDFILES_AUTHURL
Google Cloud Storage: GS_ACCESS_KEY_ID, GS_SECRET_ACCESS_KEY
Pydrive: GOOGLE_DRIVE_ACCOUNT_KEY, GOOGLE_DRIVE_SETTINGS
Swift: SWIFT_USERNAME, SWIFT_PASSWORD, SWIFT_AUTHURL, SWIFT_TENANTNAME OR SWIFT_PREAUTHURL, SWIFT_PREAUTHTOKEN

These are all I could find on that man page. S3 is missing from there, I guess that's a documentation bug in duplicity then; I'll file one.

[ede]

if you could attach a patch or even provide branch against the manpage
bin/duplicity.1
it would be even more helpful.

in case all that is not possible a preformulated text for the S3 notes section would help as well.

thx alot ..ede/duply.net

On 31.12.2015 15:07, Jonas Haag wrote:

S3: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY
Azure: AZURE_ACCOUNT_NAME, AZURE_ACCOUNT_KEY
Cloudfiles: CLOUDFILES_USERNAME, CLOUDFILES_APIKEY, CLOUDFILES_AUTHURL
Google Cloud Storage: GS_ACCESS_KEY_ID, GS_SECRET_ACCESS_KEY
Pydrive: GOOGLE_DRIVE_ACCOUNT_KEY, GOOGLE_DRIVE_SETTINGS
Swift: SWIFT_USERNAME, SWIFT_PASSWORD, SWIFT_AUTHURL, SWIFT_TENANTNAME OR SWIFT_PREAUTHURL, SWIFT_PREAUTHTOKEN

These are all I could find on that man page. S3 is missing from there, I guess that's a documentation bug in duplicity then; I'll file one.

---

** [bugs:#90] S3: TARGET_USER/PASS have no effect**

Status: open
Group: duply
Labels: s3
Created: Thu Dec 31, 2015 11:28 AM UTC by Jonas Haag
Last Updated: Thu Dec 31, 2015 01:48 PM UTC
Owner: nobody

S3: TARGET_USER and TARGET_PASS are not being passed to boto. You have to export AWS_* and not use TARGET_USER/PASS in your duply config. This is outright confusing; duply should rather export these AWS_* on its own.

---

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/ftplicity/bugs/90/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

[ede]

Jonas,

added the text to the template config. will be in the next release!

thx.. ede