Autogenerated update (2020-06-24)

Update:
- cloudbuild_v1
- cloudbuild_v1alpha1
- cloudbuild_v1alpha2
- cloudfunctions_v1
- dialogflow_v2
- dialogflow_v2beta1
- displayvideo_v1
- documentai_v1beta2
- doubleclicksearch_v2
- fcm_v1
- healthcare_v1
- healthcare_v1beta1
- monitoring_v3
- spanner_v1
- speech_v1
- speech_v1p1beta1

generated/google/apis/spanner_v1/classes.rb

@@ -190,10 +190,11 @@ module Google
         include Google::Apis::Core::Hashable
       
         # # Transactions
-        # Each session can have at most one active transaction at a time. After the
-        # active transaction is completed, the session can immediately be
-        # re-used for the next transaction. It is not necessary to create a
-        # new session for each transaction.
+        # Each session can have at most one active transaction at a time (note that
+        # standalone reads and queries use a transaction internally and do count
+        # towards the one transaction limit). After the active transaction is
+        # completed, the session can immediately be re-used for the next transaction.
+        # It is not necessary to create a new session for each transaction.
         # # Transaction Modes
         # Cloud Spanner supports three transaction modes:
         # 1. Locking read-write. This type of transaction is the only way
@@ -555,10 +556,11 @@ module Google
         attr_accessor :mutations
       
         # # Transactions
-        # Each session can have at most one active transaction at a time. After the
-        # active transaction is completed, the session can immediately be
-        # re-used for the next transaction. It is not necessary to create a
-        # new session for each transaction.
+        # Each session can have at most one active transaction at a time (note that
+        # standalone reads and queries use a transaction internally and do count
+        # towards the one transaction limit). After the active transaction is
+        # completed, the session can immediately be re-used for the next transaction.
+        # It is not necessary to create a new session for each transaction.
         # # Transaction Modes
         # Cloud Spanner supports three transaction modes:
         # 1. Locking read-write. This type of transaction is the only way
@@ -3519,10 +3521,11 @@ module Google
       end
       
       # # Transactions
-      # Each session can have at most one active transaction at a time. After the
-      # active transaction is completed, the session can immediately be
-      # re-used for the next transaction. It is not necessary to create a
-      # new session for each transaction.
+      # Each session can have at most one active transaction at a time (note that
+      # standalone reads and queries use a transaction internally and do count
+      # towards the one transaction limit). After the active transaction is
+      # completed, the session can immediately be re-used for the next transaction.
+      # It is not necessary to create a new session for each transaction.
       # # Transaction Modes
       # Cloud Spanner supports three transaction modes:
       # 1. Locking read-write. This type of transaction is the only way
@@ -3772,10 +3775,11 @@ module Google
         include Google::Apis::Core::Hashable
       
         # # Transactions
-        # Each session can have at most one active transaction at a time. After the
-        # active transaction is completed, the session can immediately be
-        # re-used for the next transaction. It is not necessary to create a
-        # new session for each transaction.
+        # Each session can have at most one active transaction at a time (note that
+        # standalone reads and queries use a transaction internally and do count
+        # towards the one transaction limit). After the active transaction is
+        # completed, the session can immediately be re-used for the next transaction.
+        # It is not necessary to create a new session for each transaction.
         # # Transaction Modes
         # Cloud Spanner supports three transaction modes:
         # 1. Locking read-write. This type of transaction is the only way
@@ -3997,10 +4001,11 @@ module Google
         attr_accessor :id
       
         # # Transactions
-        # Each session can have at most one active transaction at a time. After the
-        # active transaction is completed, the session can immediately be
-        # re-used for the next transaction. It is not necessary to create a
-        # new session for each transaction.
+        # Each session can have at most one active transaction at a time (note that
+        # standalone reads and queries use a transaction internally and do count
+        # towards the one transaction limit). After the active transaction is
+        # completed, the session can immediately be re-used for the next transaction.
+        # It is not necessary to create a new session for each transaction.
         # # Transaction Modes
         # Cloud Spanner supports three transaction modes:
         # 1. Locking read-write. This type of transaction is the only way

generated/google/apis/spanner_v1/service.rb

@@ -1299,6 +1299,8 @@ module Google
         # be queried using the Operations API.
         # @param [String] database
         #   Required. The database whose schema we wish to get.
+        #   Values are of the form
+        #   `projects/<project>/instances/<instance>/databases/<database>`
         # @param [String] fields
         #   Selector specifying which fields to include in a partial response.
         # @param [String] quota_user