instead of using your patch i opted to remove this backend specific part of duply for the sake of maintainability. with version 1.10 you will be able to place export declarations in the conf file for the env vars needed. there will be a hint in there as well just below the old auth section in new generated profile's conf files.
please try the current development version from http://duply.net/tmp/duply.sh
and tell me how that works out for you.
regards.. ede
Last edit: ede 2015-07-24
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for looking in to this. I finally got around to testing... I commented out TARGET_USER and TARGET_PASS and exported AZURE_ACCOUNT_NAME and AZURE_ACCOUNT_KEY. This caused an error:
Start duply.sh v1.9.3dev, time is 2015-07-29 21:54:53.
Using profile '/home/scott/.duply/photos'.
Sorry. A fatal ERROR occured:
Backup target credentials needed but not set in conf file
'/home/scott/.duply/photos/conf'.
Setting TARGET_USER or TARGET_PASS or the corresponding values in TARGET url
are missing. Some protocols only might need it for write access to the backup
repository (commands: bkp,backup,full,incr,purge) but not for read only access
(e.g. verify,list,restore,fetch).
Hints:
Add the credentials (user,password) to the conf file.
To force an empty password set TARGET_PASS='' or >TARGET='prot://user:@host..'.
I then tried it with TARGET_USER and TARGET_PASS populated, and the AZURE specific variables still exported, and it caused a problem for the backend by passing TARGET_USER in the URL. The backend tried to create a container called username@containername which is not a valid container name.
Once I added Azure to the list of protocols that do not need passwords (line 1765) it started working.
Regards
Scott
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That version works without any modification, thanks!
I have not performed rigorous testing though - just status, list, backup
and fetch against the Azure backend. Do you want me to perform any other
testing?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
thx alot for testing! actually a successful rw access to the backend w/ the backup action should signal that all is as expected.
regards.. ede
On 29.07.2015 22:19, Scott McKenzie wrote:
That version works without any modification, thanks!
I have not performed rigorous testing though - just status, list, backup
and fetch against the Azure backend. Do you want me to perform any other
testing?
Status: open Group: Next Release (example) Created: Wed Jan 14, 2015 10:21 AM UTC by Scott McKenzie Last Updated: Wed Jul 29, 2015 01:46 PM UTC Owner: nobody Attachments:
saw it ;)
just busy currently.. will have a look at it when time allows it. thx ede
ok,
instead of using your patch i opted to remove this backend specific part of duply for the sake of maintainability. with version 1.10 you will be able to place export declarations in the conf file for the env vars needed. there will be a hint in there as well just below the old auth section in new generated profile's conf files.
please try the current development version from
http://duply.net/tmp/duply.sh
and tell me how that works out for you.
regards.. ede
Last edit: ede 2015-07-24
Thanks for looking in to this. I finally got around to testing... I commented out TARGET_USER and TARGET_PASS and exported AZURE_ACCOUNT_NAME and AZURE_ACCOUNT_KEY. This caused an error:
I then tried it with TARGET_USER and TARGET_PASS populated, and the AZURE specific variables still exported, and it caused a problem for the backend by passing TARGET_USER in the URL. The backend tried to create a container called username@containername which is not a valid container name.
Once I added Azure to the list of protocols that do not need passwords (line 1765) it started working.
Regards
Scott
my bad. removed this check also. pls try again
http://duply.net/wiki/index.php/Duply-code#Latest_Development_Snapshot
thanks! ..ede
That version works without any modification, thanks!
I have not performed rigorous testing though - just status, list, backup
and fetch against the Azure backend. Do you want me to perform any other
testing?
thx alot for testing! actually a successful rw access to the backend w/ the backup action should signal that all is as expected.
regards.. ede
On 29.07.2015 22:19, Scott McKenzie wrote:
Related
Feature Requests:
#33