google-cloud-security-private_ca-v1 0.1.1 → 0.1.5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 00c9d5bdca4c41cc7f6163ad535cfedd094edd8b60cf50be6e24ba45da4fc71c
-  data.tar.gz: 2c6478ed8757d8185ebf918f31c3eac9ea10bc47dc0e16237b9f9cc353204f48
+  metadata.gz: 616cd3347b910c3dcbcfeff5f57a88dc4d9036fe6a03d93eab2a4f166424ffbe
+  data.tar.gz: 531cb999f2c36c594bb9e685573473a15c561216c64f11fc51c1102baf4da3b4
 SHA512:
-  metadata.gz: 64d4447d54af34351708788d14a122abb116379ddb573d23fac7e46ad23daabbc96cca6822964ba956f36fdc08fa7e807d30dc560772b10383effeb08e74c2b3
-  data.tar.gz: 29b83a06c52deefd001a5f629cb4237114e9bc180b8cbef87384a1db0abd4ecf8b5308c6d943bea210d96cab6f3a14f86997fc205587e9a50f36f54eb621c899
+  metadata.gz: bba8c2db50f9944a05945dfd1fd77c1ec3a93f99c3626d23ea06dfb490da6d9a38ac7626048bc9bc896bd2f27ba6ad1257ab1895e0c378badc73f6a74189ddff
+  data.tar.gz: 49f58218e00223aacaacb9b2c0330403a3484a026a798741723deb8086b635de3747fb893b2ca259148618e45caa9eb57fa52c753a071371aff475999d685907

data/.yardopts

@@ -1,5 +1,5 @@
 --no-private
---title=Ceritificate Authority Service V1 API
+--title="Ceritificate Authority Service V1 API"
 --exclude _pb\.rb$
 --markup markdown
 --markup-provider redcarpet

data/AUTHENTICATION.md

@@ -25,7 +25,7 @@ export PRIVATE_CA_CREDENTIALS=path/to/keyfile.json
 3. Initialize the client.
 
 ```ruby
-require "google/cloud/security/private_ca/v1"
+require "google/cloud/location"
 
 client = ::Google::Cloud::Security::PrivateCA::V1::CertificateAuthorityService::Client.new
 ```
@@ -73,7 +73,7 @@ checks for credentials are configured on the service Credentials class (such as
 * `GOOGLE_APPLICATION_CREDENTIALS` - Path to JSON file
 
 ```ruby
-require "google/cloud/security/private_ca/v1"
+require "google/cloud/location"
 
 ENV["PRIVATE_CA_CREDENTIALS"] = "path/to/keyfile.json"
 
@@ -86,7 +86,7 @@ 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/security/private_ca/v1"
+require "google/cloud/location"
 
 client = ::Google::Cloud::Security::PrivateCA::V1::CertificateAuthorityService::Client.new do |config|
   config.credentials = "path/to/keyfile.json"
@@ -96,7 +96,7 @@ end
 Or globally for all clients:
 
 ```ruby
-require "google/cloud/security/private_ca/v1"
+require "google/cloud/location"
 
 ::Google::Cloud::Security::PrivateCA::V1::CertificateAuthorityService::Client.configure do |config|
   config.credentials = "path/to/keyfile.json"
@@ -120,15 +120,6 @@ To configure your system for this, simply:
 **NOTE:** This is _not_ recommended for running in production. The Cloud SDK
 *should* only be used during development.
 
-[gce-how-to]: https://cloud.google.com/compute/docs/authentication#using
-[dev-console]: https://console.cloud.google.com/project
-
-[enable-apis]: https://raw.githubusercontent.com/GoogleCloudPlatform/gcloud-common/master/authentication/enable-apis.png
-
-[create-new-service-account]: https://raw.githubusercontent.com/GoogleCloudPlatform/gcloud-common/master/authentication/create-new-service-account.png
-[create-new-service-account-existing-keys]: https://raw.githubusercontent.com/GoogleCloudPlatform/gcloud-common/master/authentication/create-new-service-account-existing-keys.png
-[reuse-service-account]: https://raw.githubusercontent.com/GoogleCloudPlatform/gcloud-common/master/authentication/reuse-service-account.png
-
 ## Creating a Service Account
 
 Google Cloud requires **Service Account Credentials** to
@@ -139,31 +130,22 @@ If you are not running this client within
 [Google Cloud Platform environments](#google-cloud-platform-environments), you
 need a Google Developers service account.
 
-1. Visit the [Google Developers Console][dev-console].
+1. Visit the [Google Cloud Console](https://console.cloud.google.com/project).
 2. Create a new project or click on an existing project.
-3. Activate the slide-out navigation tray and select **API Manager**. From
+3. Activate the menu in the upper left and select **APIs & Services**. From
    here, you will enable the APIs that your application requires.
 
-   ![Enable the APIs that your application requires][enable-apis]
-
    *Note: You may need to enable billing in order to use these services.*
 
 4. Select **Credentials** from the side navigation.
 
-   You should see a screen like one of the following.
-
-   ![Create a new service account][create-new-service-account]
-
-   ![Create a new service account With Existing Keys][create-new-service-account-existing-keys]
-
-   Find the "Add credentials" drop down and select "Service account" to be
-   guided through downloading a new JSON key file.
+   Find the "Create credentials" drop down near the top of the page, and select
+   "Service account" to be guided through downloading a new JSON key file.
 
    If you want to re-use an existing service account, you can easily generate a
-   new key file. Just select the account you wish to re-use, and click "Generate
-   new JSON key":
-
-   ![Re-use an existing service account][reuse-service-account]
+   new key file. Just select the account you wish to re-use, click the pencil
+   tool on the right side to edit the service account, select the **Keys** tab,
+   and then select **Add Key**.
 
    The key file you download will be used by this library to authenticate API
    requests and should be stored in a secure location.