gapic-generator-cloud 0.1.3 → 0.1.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 1ebe5e42a4b47d685c1b24813b73c9f85c16b0398c8b6b63bb4cf76c201c6d1c
-  data.tar.gz: 8ed585e0d16bedf7b9f2ccd9b2b4088250d4c0bee77a2bf4793d594703867b0c
+  metadata.gz: a252fcd2176cfa70f9f5a723de32f89a071c3a385867688bde7316a6ce2a55c3
+  data.tar.gz: e461c3abd3ca2d5d60ff1c5d9419cecb467e00f33ef23674ade95cff229114de
 SHA512:
-  metadata.gz: 9d91d9b38c1dabd02c091303bce7c17a053135746f0da994e1eac68edb46d1554f8b4b37b60d9d6f1d1c27fec88d0299ec5ab388459d89669d01c0e3b4e59bc9
-  data.tar.gz: d4cea15f6a805c61a1227c6250eda1a958774d93192f965d197e78f89f3dfbc0585cf50d47165e99282d1cda28a9d989ea914cd660c46ce8577cedc5b5d39dbd
+  metadata.gz: 135ddb83ecffcfb83e09f01c544b1088b9b3266c0e2cfa54b73b16d6feb4de31f050865f16c9d595696962366cffe77e2103d2dca1d461cbbc7e5d2b3a96fd8a
+  data.tar.gz: bf334cab3f55ee23a632ee96ee1c20a82508b668d4aac4dc5bddf611c497d0fc8371679efb3d9dc860d2fe47dbe8259beec33f485bbeada12e11cbaad93f0d41

data/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Release History for gapic-generator-cloud
 
+### 0.1.4 / 2020-03-12
+
+* Includes changes from gapic-generator 0.1.4
+
 ### 0.1.3 / 2020-03-11
 
 * Includes changes from gapic-generator 0.1.3

data/lib/gapic/generator/cloud/version.rb

@@ -17,7 +17,7 @@
 module Gapic
   module Generator
     module Cloud
-      VERSION = "0.1.3"
+      VERSION = "0.1.4"
     end
   end
 end

data/templates/cloud/gem/authentication.erb

@@ -3,17 +3,18 @@
 <%- assert_locals service -%>
 # Authentication
 
-In general, the <%= gem.name %> library uses [Service
-Account](https://cloud.google.com/iam/docs/creating-managing-service-accounts)
-credentials to connect to Google Cloud services. When running within [Google
-Cloud Platform environments](#google-cloud-platform-environments)
-the credentials will be discovered automatically. When running on other
+In general, the <%= gem.name %> library uses
+[Service Account](https://cloud.google.com/iam/docs/creating-managing-service-accounts)
+credentials to connect to Google Cloud services. When running within
+[Google Cloud Platform environments](#google-cloud-platform-environments) the
+credentials will be discovered automatically. When running on other
 environments, the Service Account credentials can be specified by providing the
-path to the [JSON
-keyfile](https://cloud.google.com/iam/docs/managing-service-account-keys) for
-the account (or the JSON itself) in [environment
-variables](#environment-variables). Additionally, Cloud SDK credentials can also
-be discovered automatically, but this is only recommended during development.
+path to the
+[JSON keyfile](https://cloud.google.com/iam/docs/managing-service-account-keys)
+for the account (or the JSON itself) in
+[environment variables](#environment-variables). Additionally, Cloud SDK
+credentials can also be discovered automatically, but this is only recommended
+during development.
 
 ## Quickstart
 
@@ -49,23 +50,24 @@ without **Service Account Credentials** directly in code.
 
 ### Google Cloud Platform environments
 
-When running on Google Cloud Platform (GCP), including Google Compute Engine (GCE),
-Google Kubernetes Engine (GKE), Google App Engine (GAE), Google Cloud Functions
-(GCF) and Cloud Run, **Credentials** and are discovered
-automatically. Code should be written as if already authenticated.
+When running on Google Cloud Platform (GCP), including Google Compute Engine
+(GCE), Google Kubernetes Engine (GKE), Google App Engine (GAE), Google Cloud
+Functions (GCF) and Cloud Run, **Credentials** are discovered automatically.
+Code should be written as if already authenticated.
 
 ### Environment Variables
 
-The **Credentials JSON** can be placed in environment
-variables instead of declaring them directly in code. Each service has its own
-environment variable, allowing for different service accounts to be used for
-different services. (See the READMEs for the individual service gems for
-details.) The path to the **Credentials JSON** file can be stored in the
-environment variable, or the **Credentials JSON** itself can be stored for
-environments such as Docker containers where writing files is difficult or not
-encouraged.
+The **Credentials JSON** can be placed in environment variables instead of
+declaring them directly in code. Each service has its own environment variable,
+allowing for different service accounts to be used for different services. (See
+the READMEs for the individual service gems for details.) The path to the
+**Credentials JSON** file can be stored in the environment variable, or the
+**Credentials JSON** itself can be stored for environments such as Docker
+containers where writing files is difficult or not encouraged.
 
-The environment variables that <%= gem.name %> checks for credentials are configured on the service Credentials class (such as {<%= service.credentials_name_full %>}):
+The environment variables that <%= gem.name %>
+checks for credentials are configured on the service Credentials class (such as
+{<%= service.credentials_name_full %>}):
 
 1. `<%= gem.env_prefix %>_CREDENTIALS` - Path to JSON file, or JSON contents
 2. `<%= gem.env_prefix %>_KEYFILE` - Path to JSON file, or JSON contents
@@ -83,7 +85,8 @@ client = <%= service.client_name_full %>.new
 
 ### Configuration
 
-The **Credentials JSON** can be configured instead of placing them in environment variables. Either on an individual client initialization:
+The **Credentials JSON** can be configured instead of placing them in
+environment variables. Either on an individual client initialization:
 
 ```ruby
 require "<%= service.package.package_require %>"
@@ -140,15 +143,15 @@ environments](#google-cloud-platform-environments), you need a Google
 Developers service account.
 
 1. Visit the [Google Developers Console][dev-console].
-1. Create a new project or click on an existing project.
-1. Activate the slide-out navigation tray and select **API Manager**. From
+2. Create a new project or click on an existing project.
+3. Activate the slide-out navigation tray and select **API Manager**. 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.*
 
-1. Select **Credentials** from the side navigation.
+4. Select **Credentials** from the side navigation.
 
    You should see a screen like one of the following.
 

data/templates/cloud/gem/gitignore.erb

@@ -16,6 +16,8 @@ pkg/*
 # Ignore files commonly present in certain dev environments
 .vagrant
 .DS_STORE
+.idea
+*.iml
 
 # Ignore synth output
 __pycache__

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: gapic-generator-cloud
 version: !ruby/object:Gem::Version
-  version: 0.1.3
+  version: 0.1.4
 platform: ruby
 authors:
 - Ernest Landrito
@@ -10,7 +10,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2020-03-11 00:00:00.000000000 Z
+date: 2020-03-12 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: actionpack