google-apis-firestore_v1beta1 0.55.0 → 0.56.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 10a160e4ae81e9230bec49a459b8fb1d5b64c62506fedf5f34b4bb8535ed7fb7
-  data.tar.gz: 68c3e0874d4e116b3ec13f19ba69a809db4bbb6e53f6f13e7d191dd41b5a5b05
+  metadata.gz: 88fc6263869932e29144b5e0f58f73a8405051f8443babafadbd150a7846a628
+  data.tar.gz: c3725e69ee08704f2d268b950b360e8f8827f7434a986f03b6abaebc58cdbdb3
 SHA512:
-  metadata.gz: cd6829ac27c16e92cdae34f8c63d9a66369efbd7d4d3211bc0f230d6a3df11788a82a097cdd47efc21101055d7a57ea5f7ff7a9791a656c7772126a1d7b5ec9a
-  data.tar.gz: dc5ca178520534576e0484f105be6fe70732e94a19a34ca5e089b28fed7092a37550d1ba06c7abf5b77b6c7de0d61b51ee1251729314bf7e3c1c8fe5d9568b34
+  metadata.gz: c0ae552a0bef900666d6a4d0aa4c6700cdd567e6494f931b77cd1637734d75603fd1a31c07c2ac7e3f65d54508f20c535a0bbaa841c5296beea82ea3521248c1
+  data.tar.gz: 5e129a40feae70e69fbe4af777daf63fdeb96fffd5c3d360631e8704939462690b68bd1d55c1f9e685fce3f3b38c7f7ae89373e38680a8068f6c243c65804313

data/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Release history for google-apis-firestore_v1beta1
 
+### v0.56.0 (2026-08-30)
+
+* Regenerated from discovery document revision 20260818
+
 ### v0.55.0 (2026-08-23)
 
 * Regenerated from discovery document revision 20260810

data/lib/google/apis/firestore_v1beta1/classes.rb

@@ -180,7 +180,7 @@ module Google
         # @return [String]
         attr_accessor :read_time
       
-        # Options for a server request.
+        # Options for a request.
         # Corresponds to the JSON property `requestOptions`
         # @return [Google::Apis::FirestoreV1beta1::RequestOptions]
         attr_accessor :request_options
@@ -258,7 +258,7 @@ module Google
         # @return [Hash<String,String>]
         attr_accessor :labels
       
-        # Options for a server request.
+        # Options for a request.
         # Corresponds to the JSON property `requestOptions`
         # @return [Google::Apis::FirestoreV1beta1::RequestOptions]
         attr_accessor :request_options
@@ -318,7 +318,7 @@ module Google
         # @return [Google::Apis::FirestoreV1beta1::TransactionOptions]
         attr_accessor :options
       
-        # Options for a server request.
+        # Options for a request.
         # Corresponds to the JSON property `requestOptions`
         # @return [Google::Apis::FirestoreV1beta1::RequestOptions]
         attr_accessor :request_options
@@ -468,7 +468,7 @@ module Google
       class CommitRequest
         include Google::Apis::Core::Hashable
       
-        # Options for a server request.
+        # Options for a request.
         # Corresponds to the JSON property `requestOptions`
         # @return [Google::Apis::FirestoreV1beta1::RequestOptions]
         attr_accessor :request_options
@@ -875,7 +875,7 @@ module Google
         # @return [String]
         attr_accessor :read_time
       
-        # Options for a server request.
+        # Options for a request.
         # Corresponds to the JSON property `requestOptions`
         # @return [Google::Apis::FirestoreV1beta1::RequestOptions]
         attr_accessor :request_options
@@ -2129,7 +2129,7 @@ module Google
         # @return [String]
         attr_accessor :read_time
       
-        # Options for a server request.
+        # Options for a request.
         # Corresponds to the JSON property `requestOptions`
         # @return [Google::Apis::FirestoreV1beta1::RequestOptions]
         attr_accessor :request_options
@@ -2217,7 +2217,7 @@ module Google
         # @return [Fixnum]
         attr_accessor :remove_target
       
-        # Options for a server request.
+        # Options for a request.
         # Corresponds to the JSON property `requestOptions`
         # @return [Google::Apis::FirestoreV1beta1::RequestOptions]
         attr_accessor :request_options
@@ -2378,7 +2378,7 @@ module Google
         # @return [String]
         attr_accessor :read_time
       
-        # Options for a server request.
+        # Options for a request.
         # Corresponds to the JSON property `requestOptions`
         # @return [Google::Apis::FirestoreV1beta1::RequestOptions]
         attr_accessor :request_options
@@ -2611,11 +2611,31 @@ module Google
         end
       end
       
-      # Options for a server request.
+      # Options for a request.
       class RequestOptions
         include Google::Apis::Core::Hashable
       
-        # Optional. The request tags for the request.
+        # Optional. The request tags for the request. Request tags are user-provided
+        # strings used for usage monitoring, cost management, and observability. Callers
+        # can associate custom application context (such as component, microservice,
+        # feature name, or operation type) with database requests. These tags are
+        # collected and aggregated in usage and monitoring reports, allowing billable
+        # operations and usage metrics to be sliced and analyzed by tag. These tags *
+        # only* show up in monitoring and are visible in administrative operations (such
+        # as usage reports). They do not affect data storage, query semantics, or
+        # request execution. Cardinality and Best Practices: - Request tags are most
+        # effective when using a bounded set of distinct values (e.g., fewer than 100
+        # distinct tags across an entire database). Using a large number of distinct
+        # tags may result in tags being omitted from top usage dashboards. - Use
+        # structured identifiers (for example: `app=cart`, `env=prod`, `service=checkout`
+        # ) and avoid high-cardinality values such as UUIDs, request IDs, timestamps,
+        # user IDs, or document keys. - Do not include sensitive data or personally
+        # identifiable information (PII) in request tags, as they show up in
+        # administrative monitoring. The tags are processed as follows: - Leading and
+        # trailing whitespace is trimmed. - Empty tags (after trimming) are filtered out.
+        # - Truncated to a maximum of 510 characters. - Deduplicated within the same
+        # request. - Limited to a maximum of 50 tags per request (excess tags are
+        # silently discarded).
         # Corresponds to the JSON property `requestTags`
         # @return [Array<String>]
         attr_accessor :request_tags
@@ -2634,7 +2654,7 @@ module Google
       class RollbackRequest
         include Google::Apis::Core::Hashable
       
-        # Options for a server request.
+        # Options for a request.
         # Corresponds to the JSON property `requestOptions`
         # @return [Google::Apis::FirestoreV1beta1::RequestOptions]
         attr_accessor :request_options
@@ -2677,7 +2697,7 @@ module Google
         # @return [String]
         attr_accessor :read_time
       
-        # Options for a server request.
+        # Options for a request.
         # Corresponds to the JSON property `requestOptions`
         # @return [Google::Apis::FirestoreV1beta1::RequestOptions]
         attr_accessor :request_options
@@ -2775,7 +2795,7 @@ module Google
         # @return [String]
         attr_accessor :read_time
       
-        # Options for a server request.
+        # Options for a request.
         # Corresponds to the JSON property `requestOptions`
         # @return [Google::Apis::FirestoreV1beta1::RequestOptions]
         attr_accessor :request_options
@@ -3499,7 +3519,7 @@ module Google
         # @return [Hash<String,String>]
         attr_accessor :labels
       
-        # Options for a server request.
+        # Options for a request.
         # Corresponds to the JSON property `requestOptions`
         # @return [Google::Apis::FirestoreV1beta1::RequestOptions]
         attr_accessor :request_options

data/lib/google/apis/firestore_v1beta1/gem_version.rb

@@ -16,13 +16,13 @@ module Google
   module Apis
     module FirestoreV1beta1
       # Version of the google-apis-firestore_v1beta1 gem
-      GEM_VERSION = "0.55.0"
+      GEM_VERSION = "0.56.0"
 
       # Version of the code generator used to generate this client
       GENERATOR_VERSION = "0.19.0"
 
       # Revision of the discovery document this client was generated from
-      REVISION = "20260810"
+      REVISION = "20260818"
     end
   end
 end

data/lib/google/apis/firestore_v1beta1/service.rb

@@ -287,7 +287,27 @@ module Google
         #   The list of field paths in the mask. See Document.fields for a field path
         #   syntax reference.
         # @param [Array<String>, String] request_options_request_tags
-        #   Optional. The request tags for the request.
+        #   Optional. The request tags for the request. Request tags are user-provided
+        #   strings used for usage monitoring, cost management, and observability. Callers
+        #   can associate custom application context (such as component, microservice,
+        #   feature name, or operation type) with database requests. These tags are
+        #   collected and aggregated in usage and monitoring reports, allowing billable
+        #   operations and usage metrics to be sliced and analyzed by tag. These tags *
+        #   only* show up in monitoring and are visible in administrative operations (such
+        #   as usage reports). They do not affect data storage, query semantics, or
+        #   request execution. Cardinality and Best Practices: - Request tags are most
+        #   effective when using a bounded set of distinct values (e.g., fewer than 100
+        #   distinct tags across an entire database). Using a large number of distinct
+        #   tags may result in tags being omitted from top usage dashboards. - Use
+        #   structured identifiers (for example: `app=cart`, `env=prod`, `service=checkout`
+        #   ) and avoid high-cardinality values such as UUIDs, request IDs, timestamps,
+        #   user IDs, or document keys. - Do not include sensitive data or personally
+        #   identifiable information (PII) in request tags, as they show up in
+        #   administrative monitoring. The tags are processed as follows: - Leading and
+        #   trailing whitespace is trimmed. - Empty tags (after trimming) are filtered out.
+        #   - Truncated to a maximum of 510 characters. - Deduplicated within the same
+        #   request. - Limited to a maximum of 50 tags per request (excess tags are
+        #   silently discarded).
         # @param [String] fields
         #   Selector specifying which fields to include in a partial response.
         # @param [String] quota_user
@@ -332,7 +352,27 @@ module Google
         #   When set, the target document must exist and have been last updated at that
         #   time. Timestamp must be microsecond aligned.
         # @param [Array<String>, String] request_options_request_tags
-        #   Optional. The request tags for the request.
+        #   Optional. The request tags for the request. Request tags are user-provided
+        #   strings used for usage monitoring, cost management, and observability. Callers
+        #   can associate custom application context (such as component, microservice,
+        #   feature name, or operation type) with database requests. These tags are
+        #   collected and aggregated in usage and monitoring reports, allowing billable
+        #   operations and usage metrics to be sliced and analyzed by tag. These tags *
+        #   only* show up in monitoring and are visible in administrative operations (such
+        #   as usage reports). They do not affect data storage, query semantics, or
+        #   request execution. Cardinality and Best Practices: - Request tags are most
+        #   effective when using a bounded set of distinct values (e.g., fewer than 100
+        #   distinct tags across an entire database). Using a large number of distinct
+        #   tags may result in tags being omitted from top usage dashboards. - Use
+        #   structured identifiers (for example: `app=cart`, `env=prod`, `service=checkout`
+        #   ) and avoid high-cardinality values such as UUIDs, request IDs, timestamps,
+        #   user IDs, or document keys. - Do not include sensitive data or personally
+        #   identifiable information (PII) in request tags, as they show up in
+        #   administrative monitoring. The tags are processed as follows: - Leading and
+        #   trailing whitespace is trimmed. - Empty tags (after trimming) are filtered out.
+        #   - Truncated to a maximum of 510 characters. - Deduplicated within the same
+        #   request. - Limited to a maximum of 50 tags per request (excess tags are
+        #   silently discarded).
         # @param [String] fields
         #   Selector specifying which fields to include in a partial response.
         # @param [String] quota_user
@@ -410,7 +450,27 @@ module Google
         #   Recovery is enabled, can additionally be a whole minute timestamp within the
         #   past 7 days.
         # @param [Array<String>, String] request_options_request_tags
-        #   Optional. The request tags for the request.
+        #   Optional. The request tags for the request. Request tags are user-provided
+        #   strings used for usage monitoring, cost management, and observability. Callers
+        #   can associate custom application context (such as component, microservice,
+        #   feature name, or operation type) with database requests. These tags are
+        #   collected and aggregated in usage and monitoring reports, allowing billable
+        #   operations and usage metrics to be sliced and analyzed by tag. These tags *
+        #   only* show up in monitoring and are visible in administrative operations (such
+        #   as usage reports). They do not affect data storage, query semantics, or
+        #   request execution. Cardinality and Best Practices: - Request tags are most
+        #   effective when using a bounded set of distinct values (e.g., fewer than 100
+        #   distinct tags across an entire database). Using a large number of distinct
+        #   tags may result in tags being omitted from top usage dashboards. - Use
+        #   structured identifiers (for example: `app=cart`, `env=prod`, `service=checkout`
+        #   ) and avoid high-cardinality values such as UUIDs, request IDs, timestamps,
+        #   user IDs, or document keys. - Do not include sensitive data or personally
+        #   identifiable information (PII) in request tags, as they show up in
+        #   administrative monitoring. The tags are processed as follows: - Leading and
+        #   trailing whitespace is trimmed. - Empty tags (after trimming) are filtered out.
+        #   - Truncated to a maximum of 510 characters. - Deduplicated within the same
+        #   request. - Limited to a maximum of 50 tags per request (excess tags are
+        #   silently discarded).
         # @param [String] transaction
         #   Reads the document in a transaction.
         # @param [String] fields
@@ -483,7 +543,27 @@ module Google
         #   nested immediately under the parent. Requests with `recursive` may not specify
         #   `show_missing`.
         # @param [Array<String>, String] request_options_request_tags
-        #   Optional. The request tags for the request.
+        #   Optional. The request tags for the request. Request tags are user-provided
+        #   strings used for usage monitoring, cost management, and observability. Callers
+        #   can associate custom application context (such as component, microservice,
+        #   feature name, or operation type) with database requests. These tags are
+        #   collected and aggregated in usage and monitoring reports, allowing billable
+        #   operations and usage metrics to be sliced and analyzed by tag. These tags *
+        #   only* show up in monitoring and are visible in administrative operations (such
+        #   as usage reports). They do not affect data storage, query semantics, or
+        #   request execution. Cardinality and Best Practices: - Request tags are most
+        #   effective when using a bounded set of distinct values (e.g., fewer than 100
+        #   distinct tags across an entire database). Using a large number of distinct
+        #   tags may result in tags being omitted from top usage dashboards. - Use
+        #   structured identifiers (for example: `app=cart`, `env=prod`, `service=checkout`
+        #   ) and avoid high-cardinality values such as UUIDs, request IDs, timestamps,
+        #   user IDs, or document keys. - Do not include sensitive data or personally
+        #   identifiable information (PII) in request tags, as they show up in
+        #   administrative monitoring. The tags are processed as follows: - Leading and
+        #   trailing whitespace is trimmed. - Empty tags (after trimming) are filtered out.
+        #   - Truncated to a maximum of 510 characters. - Deduplicated within the same
+        #   request. - Limited to a maximum of 50 tags per request (excess tags are
+        #   silently discarded).
         # @param [Boolean] show_missing
         #   If the list should show missing documents. A document is missing if it does
         #   not exist, but there are sub-documents nested underneath it. When true, such
@@ -604,7 +684,27 @@ module Google
         #   nested immediately under the parent. Requests with `recursive` may not specify
         #   `show_missing`.
         # @param [Array<String>, String] request_options_request_tags
-        #   Optional. The request tags for the request.
+        #   Optional. The request tags for the request. Request tags are user-provided
+        #   strings used for usage monitoring, cost management, and observability. Callers
+        #   can associate custom application context (such as component, microservice,
+        #   feature name, or operation type) with database requests. These tags are
+        #   collected and aggregated in usage and monitoring reports, allowing billable
+        #   operations and usage metrics to be sliced and analyzed by tag. These tags *
+        #   only* show up in monitoring and are visible in administrative operations (such
+        #   as usage reports). They do not affect data storage, query semantics, or
+        #   request execution. Cardinality and Best Practices: - Request tags are most
+        #   effective when using a bounded set of distinct values (e.g., fewer than 100
+        #   distinct tags across an entire database). Using a large number of distinct
+        #   tags may result in tags being omitted from top usage dashboards. - Use
+        #   structured identifiers (for example: `app=cart`, `env=prod`, `service=checkout`
+        #   ) and avoid high-cardinality values such as UUIDs, request IDs, timestamps,
+        #   user IDs, or document keys. - Do not include sensitive data or personally
+        #   identifiable information (PII) in request tags, as they show up in
+        #   administrative monitoring. The tags are processed as follows: - Leading and
+        #   trailing whitespace is trimmed. - Empty tags (after trimming) are filtered out.
+        #   - Truncated to a maximum of 510 characters. - Deduplicated within the same
+        #   request. - Limited to a maximum of 50 tags per request (excess tags are
+        #   silently discarded).
         # @param [Boolean] show_missing
         #   If the list should show missing documents. A document is missing if it does
         #   not exist, but there are sub-documents nested underneath it. When true, such
@@ -737,7 +837,27 @@ module Google
         #   The list of field paths in the mask. See Document.fields for a field path
         #   syntax reference.
         # @param [Array<String>, String] request_options_request_tags
-        #   Optional. The request tags for the request.
+        #   Optional. The request tags for the request. Request tags are user-provided
+        #   strings used for usage monitoring, cost management, and observability. Callers
+        #   can associate custom application context (such as component, microservice,
+        #   feature name, or operation type) with database requests. These tags are
+        #   collected and aggregated in usage and monitoring reports, allowing billable
+        #   operations and usage metrics to be sliced and analyzed by tag. These tags *
+        #   only* show up in monitoring and are visible in administrative operations (such
+        #   as usage reports). They do not affect data storage, query semantics, or
+        #   request execution. Cardinality and Best Practices: - Request tags are most
+        #   effective when using a bounded set of distinct values (e.g., fewer than 100
+        #   distinct tags across an entire database). Using a large number of distinct
+        #   tags may result in tags being omitted from top usage dashboards. - Use
+        #   structured identifiers (for example: `app=cart`, `env=prod`, `service=checkout`
+        #   ) and avoid high-cardinality values such as UUIDs, request IDs, timestamps,
+        #   user IDs, or document keys. - Do not include sensitive data or personally
+        #   identifiable information (PII) in request tags, as they show up in
+        #   administrative monitoring. The tags are processed as follows: - Leading and
+        #   trailing whitespace is trimmed. - Empty tags (after trimming) are filtered out.
+        #   - Truncated to a maximum of 510 characters. - Deduplicated within the same
+        #   request. - Limited to a maximum of 50 tags per request (excess tags are
+        #   silently discarded).
         # @param [Array<String>, String] update_mask_field_paths
         #   The list of field paths in the mask. See Document.fields for a field path
         #   syntax reference.

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: google-apis-firestore_v1beta1
 version: !ruby/object:Gem::Version
-  version: 0.55.0
+  version: 0.56.0
 platform: ruby
 authors:
 - Google LLC
@@ -57,7 +57,7 @@ licenses:
 metadata:
   bug_tracker_uri: https://github.com/googleapis/google-api-ruby-client/issues
   changelog_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-firestore_v1beta1/CHANGELOG.md
-  documentation_uri: https://googleapis.dev/ruby/google-apis-firestore_v1beta1/v0.55.0
+  documentation_uri: https://googleapis.dev/ruby/google-apis-firestore_v1beta1/v0.56.0
   source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-firestore_v1beta1
 rdoc_options: []
 require_paths: