TrueCloudLab/restic
16
0
Fork 2
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

Fix small things left open by #1552

Browse source
This commit is contained in:
Alexander Neumann 2018-03-18 19:54:12 +01:00
parent 8206f85d2e
commit 3cd8a7bc96
2 changed files with 2 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
changelog/unreleased/pull-1552
View file

@ -9,4 +9,5 @@ the additional capabilities to auth from Google's internal metadata endpoints.
For users running restic in GCP this can make authentication far easier than it
was before.
https://github.com/restic/restic/pull/1552
https://developers.google.com/identity/protocols/application-default-credentials

2
doc/030_preparing_a_new_repo.rst
View file

@ -362,7 +362,7 @@ key file and the project ID as follows:
$ export GOOGLE_PROJECT_ID=123123123123
$ export GOOGLE_APPLICATION_CREDENTIALS=$HOME/.config/gs-secret-restic-key.json
We use Google's client library to generate [default authentication
Restic uses Google's client library to generate [default authentication
material](https://developers.google.com/identity/protocols/application-default-credentials),
which means if you're running in Google Container Engine or are otherwise
located on an instance with default service accounts then these should work out