From 3cd8a7bc9688b22ab0cc82ff951ea2259f268ce5 Mon Sep 17 00:00:00 2001 From: Alexander Neumann Date: Sun, 18 Mar 2018 19:54:12 +0100 Subject: [PATCH] Fix small things left open by #1552 --- changelog/unreleased/pull-1552 | 1 + doc/030_preparing_a_new_repo.rst | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/changelog/unreleased/pull-1552 b/changelog/unreleased/pull-1552 index f97a60f06..244a334ee 100644 --- a/changelog/unreleased/pull-1552 +++ b/changelog/unreleased/pull-1552 @@ -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 diff --git a/doc/030_preparing_a_new_repo.rst b/doc/030_preparing_a_new_repo.rst index 1b984c4a7..44f8db365 100644 --- a/doc/030_preparing_a_new_repo.rst +++ b/doc/030_preparing_a_new_repo.rst @@ -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