Replies: 1 comment 2 replies
-
Went ahead and implemented this in 87b7f76, this will go out with the v1.0.0 release in a few weeks. References of the form MY_VAR=${MY_FOO_VAR} will be supported |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
We are currently starting the backrest container and passing environment variables like AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, RESTIC_PASSWORD to the container. This helps us to setup the repo in config.json
. Now we would like to add more repos and tried to define the variables like AWS_SECRET_ACCESS_KEY for repo2 like this from a variable REPO2_AWS_ACCESS_KEY_ID:
It seems that AWS_ACCESS_KEY_ID for repo2 is not using the env variable. Is there any way to archive that?
Background: we prefer using env. variables as those are not printed out in the webgui. We have some users, who should be able to restore and authenticate on an apache reverse proxy before backrest UI. We do not want give away AWS_ACCESS_KEY_ID... but enable the user to restore from the UI.
Our workaround would be to have one backrest instance per repo, but it would easier for the user to have all in one webgui.
Thanks and best regards,
Andreas
Beta Was this translation helpful? Give feedback.
All reactions