google-cloud-spanner-admin-database-v1 0.7.1 → 0.7.5

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 17e28393f9f5491b7a57603ce730e4d9bdb2cc65dbcdc4371a92d4923185f0f7
4
- data.tar.gz: 0b64716e82450dc175de2aefdf8de7c830aee35868308ff9e5a872c04436d0d3
3
+ metadata.gz: 38328804718433b12c9422707c62c5a2860f6d49d9e30e2b5618386fd039967c
4
+ data.tar.gz: f688ab1055a703babe7cfd2198c23c9f725380fe01773373a67b4a9c4ac3284a
5
5
  SHA512:
6
- metadata.gz: b98b1a94e0b63d0dcc2adbd84b76e0ba34160de40206b9ac5f512c929cef0f12e0d78a38f61dad01a80c584987d4eaa272252310c953b2a5e599ed020dafc7b4
7
- data.tar.gz: f51a80bc43e106a18b939993fd5f48ffbddea4fbe460c23645f708278013e30add992bb5015a3d6d4ae33f4fa1fe6c3311f2e8d58f590b3bd5a4f945be209db7
6
+ metadata.gz: ba3ec39b5f1263114c9e56734e8df0ac372909858b432d736abd5f558c2e5e6f51a61ab96c8eb110d240bd16895e3b419239916ec689b1fe40bc5ca220ee86a5
7
+ data.tar.gz: 9fc030210c542c23e65bcecc9a941a906950bbf7c8295210aa4e0e6d509945a5b761fdabcf48cc200e3fb6ced559d000af3d9e21851b17a340b6bccba77a8399
data/.yardopts CHANGED
@@ -1,5 +1,5 @@
1
1
  --no-private
2
- --title=Cloud Spanner Database Admin V1 API
2
+ --title="Cloud Spanner Database Admin V1 API"
3
3
  --exclude _pb\.rb$
4
4
  --markup markdown
5
5
  --markup-provider redcarpet
data/AUTHENTICATION.md CHANGED
@@ -120,15 +120,6 @@ To configure your system for this, simply:
120
120
  **NOTE:** This is _not_ recommended for running in production. The Cloud SDK
121
121
  *should* only be used during development.
122
122
 
123
- [gce-how-to]: https://cloud.google.com/compute/docs/authentication#using
124
- [dev-console]: https://console.cloud.google.com/project
125
-
126
- [enable-apis]: https://raw.githubusercontent.com/GoogleCloudPlatform/gcloud-common/master/authentication/enable-apis.png
127
-
128
- [create-new-service-account]: https://raw.githubusercontent.com/GoogleCloudPlatform/gcloud-common/master/authentication/create-new-service-account.png
129
- [create-new-service-account-existing-keys]: https://raw.githubusercontent.com/GoogleCloudPlatform/gcloud-common/master/authentication/create-new-service-account-existing-keys.png
130
- [reuse-service-account]: https://raw.githubusercontent.com/GoogleCloudPlatform/gcloud-common/master/authentication/reuse-service-account.png
131
-
132
123
  ## Creating a Service Account
133
124
 
134
125
  Google Cloud requires **Service Account Credentials** to
@@ -139,31 +130,22 @@ If you are not running this client within
139
130
  [Google Cloud Platform environments](#google-cloud-platform-environments), you
140
131
  need a Google Developers service account.
141
132
 
142
- 1. Visit the [Google Developers Console][dev-console].
133
+ 1. Visit the [Google Cloud Console](https://console.cloud.google.com/project).
143
134
  2. Create a new project or click on an existing project.
144
- 3. Activate the slide-out navigation tray and select **API Manager**. From
135
+ 3. Activate the menu in the upper left and select **APIs & Services**. From
145
136
  here, you will enable the APIs that your application requires.
146
137
 
147
- ![Enable the APIs that your application requires][enable-apis]
148
-
149
138
  *Note: You may need to enable billing in order to use these services.*
150
139
 
151
140
  4. Select **Credentials** from the side navigation.
152
141
 
153
- You should see a screen like one of the following.
154
-
155
- ![Create a new service account][create-new-service-account]
156
-
157
- ![Create a new service account With Existing Keys][create-new-service-account-existing-keys]
158
-
159
- Find the "Add credentials" drop down and select "Service account" to be
160
- guided through downloading a new JSON key file.
142
+ Find the "Create credentials" drop down near the top of the page, and select
143
+ "Service account" to be guided through downloading a new JSON key file.
161
144
 
162
145
  If you want to re-use an existing service account, you can easily generate a
163
- new key file. Just select the account you wish to re-use, and click "Generate
164
- new JSON key":
165
-
166
- ![Re-use an existing service account][reuse-service-account]
146
+ new key file. Just select the account you wish to re-use, click the pencil
147
+ tool on the right side to edit the service account, select the **Keys** tab,
148
+ and then select **Add Key**.
167
149
 
168
150
  The key file you download will be used by this library to authenticate API
169
151
  requests and should be stored in a secure location.
data/README.md CHANGED
@@ -9,7 +9,7 @@ https://github.com/googleapis/google-cloud-ruby
9
9
  This gem is a _versioned_ client. It provides basic client classes for a
10
10
  specific version of the Cloud Spanner Database Admin V1 API. Most users should consider using
11
11
  the main client gem,
12
- [google-cloud-spanner-admin-database](https://rubygems.org/gems/google-cloud-spanner-admin-database).
12
+ [google-cloud-spanner](https://rubygems.org/gems/google-cloud-spanner).
13
13
  See the section below titled *Which client should I use?* for more information.
14
14
 
15
15
  ## Installation
@@ -83,7 +83,7 @@ about the Ruby support schedule.
83
83
  ## Which client should I use?
84
84
 
85
85
  Most modern Ruby client libraries for Google APIs come in two flavors: the main
86
- client library with a name such as `google-cloud-spanner-admin-database`,
86
+ client library with a name such as `google-cloud-spanner`,
87
87
  and lower-level _versioned_ client libraries with names such as
88
88
  `google-cloud-spanner-admin-database-v1`.
89
89
  _In most cases, you should install the main client._
@@ -110,7 +110,7 @@ service version.
110
110
 
111
111
  We recommend that most users install the main client gem for a service. You can
112
112
  identify this gem as the one _without_ a version in its name, e.g.
113
- `google-cloud-spanner-admin-database`.
113
+ `google-cloud-spanner`.
114
114
  The main client is recommended because it will embody the best practices for
115
115
  accessing the service, and may also provide more convenient interfaces or
116
116
  tighter integration into frameworks and third-party libraries. In addition, the