AUTHENTICATION.md in google-cloud-secret_manager-v1-0.10.1 vs AUTHENTICATION.md in google-cloud-secret_manager-v1-0.10.2

- old
+ new

@@ -64,15 +64,15 @@ The environment variables that google-cloud-secret_manager-v1 checks for credentials are configured on the service Credentials class (such as {::Google::Cloud::SecretManager::V1::SecretManagerService::Credentials}): -1. `SECRET_MANAGER_CREDENTIALS` - Path to JSON file, or JSON contents -2. `SECRET_MANAGER_KEYFILE` - Path to JSON file, or JSON contents -3. `GOOGLE_CLOUD_CREDENTIALS` - Path to JSON file, or JSON contents -4. `GOOGLE_CLOUD_KEYFILE` - Path to JSON file, or JSON contents -5. `GOOGLE_APPLICATION_CREDENTIALS` - Path to JSON file +* `SECRET_MANAGER_CREDENTIALS` - Path to JSON file, or JSON contents +* `SECRET_MANAGER_KEYFILE` - Path to JSON file, or JSON contents +* `GOOGLE_CLOUD_CREDENTIALS` - Path to JSON file, or JSON contents +* `GOOGLE_CLOUD_KEYFILE` - Path to JSON file, or JSON contents +* `GOOGLE_APPLICATION_CREDENTIALS` - Path to JSON file ```ruby require "google/cloud/secret_manager/v1" ENV["SECRET_MANAGER_CREDENTIALS"] = "path/to/keyfile.json" @@ -80,21 +80,21 @@ client = ::Google::Cloud::SecretManager::V1::SecretManagerService::Client.new ``` ### Configuration -The **Credentials JSON** can be configured instead of placing them in -environment variables. Either on an individual client initialization: +The path to the **Credentials JSON** file can be configured instead of storing +it in an environment variable. Either on an individual client initialization: ```ruby require "google/cloud/secret_manager/v1" client = ::Google::Cloud::SecretManager::V1::SecretManagerService::Client.new do |config| config.credentials = "path/to/keyfile.json" end ``` -Or configured globally for all clients: +Or globally for all clients: ```ruby require "google/cloud/secret_manager/v1" ::Google::Cloud::SecretManager::V1::SecretManagerService::Client.configure do |config|