docs (Consul Enterprise): Google Cloud Storage snapshot documentation (#6480)

This commit is contained in:
Hans Hasselberg 2019-09-13 17:54:15 +02:00 committed by GitHub
parent bdb3a9792e
commit 62de041a36
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 17 additions and 0 deletions

View File

@ -122,6 +122,9 @@ Usage: `consul snapshot agent [options]`
"account_name": "", "account_name": "",
"account_key": "", "account_key": "",
"container_name": "" "container_name": ""
},
"google_storage": {
"bucket": ""
} }
} }
} }
@ -277,6 +280,20 @@ From Consul Enterprise version `1.5.0` onwards, you can store snapshots in Azure
* `-azure-blob-container-name` - Container to use. Required for Azure blob storage, and setting this * `-azure-blob-container-name` - Container to use. Required for Azure blob storage, and setting this
disables local storage. disables local storage.
#### Google Cloud Storage options
From Consul Enterprise version `1.6.1` onwards, you can store snapshots in Google Cloud Storage. Authentication relies on automatic discovery through the sdk as described [here](https://cloud.google.com/docs/authentication/production):
* First, ADC checks to see if the environment variable GOOGLE_APPLICATION_CREDENTIALS is set. If the variable is set, ADC uses the service account file that the variable points to. The next section describes how to set the environment variable.
* If the environment variable isn't set, ADC uses the default service account that Compute Engine, Kubernetes Engine, App Engine, and Cloud Functions provide, for applications that run on those services.
* If ADC can't use either of the above credentials, an error occurs.
This integration needs the following information:
* `-gcs-bucket` supplies the bucket to use.
## Examples ## Examples
Running the agent with no arguments will run a long-running daemon process that will Running the agent with no arguments will run a long-running daemon process that will