Project

General

Profile

Feature #3895

applying settings via shell commands

Added by yoav over 5 years ago. Updated over 5 years ago.

Status:
Confirmed
Priority:
Low
Assignee:
Category:
backupninja
Target version:
-
Start date:
04/20/2012
Due date:
% Done:

0%

QA Check:

Description

I noticed that some parameters can be set to be retrieved via executing shell commands. For example, on my .dup script I use:

PASSWORD = `cat /path/to/gpg_passphrase.txt`

and it works great! (because in the dup handler, it is set via `export PASSPHRASE=$password`.)

However, when I try to do the same with my AWS key/secret, it fails, e.g.

awsaccesskeyid = `cat /path/to/aws_access_key_id`

won't work, because the script is assigning it using `export AWS_ACCESS_KEY_ID="$awsaccesskeyid"`.

I think it would be very useful to assign both / all parameter such that they can be retrieved externally this way...

Can this change be considered??

Thanks in advance
Yoav

History

#1 Updated by yoav over 5 years ago

actually, I'm not sure why. Even after changing the export command without the quotes it seems to treat the string as is. I also tried using things like

awsaccesskeyid = ${AWS_ACCESS_KEY_ID}

and then setting an environment variable. It works fine with the GPG passphrase, and also the dest_url (using something like desturl = s3+http://backups/${HOSTNAME}/daily/). For some reason however, it doesn't jive with the AWS settings...

#2 Updated by intrigeri over 5 years ago

  • Category set to backupninja
  • Status changed from New to Confirmed
  • Assignee set to yoav
  • Priority changed from Normal to Low

Hi. Feel free to consistently add support for this in every handler if you wish.

Also available in: Atom PDF