google-cloud-storage_batch_operations-v1 0.a → 0.1.1

data/proto_docs/google/protobuf/duration.rb

@@ -0,0 +1,98 @@
+# frozen_string_literal: true
+
+# Copyright 2025 Google LLC
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#     https://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+# Auto-generated by gapic-generator-ruby. DO NOT EDIT!
+
+
+module Google
+  module Protobuf
+    # A Duration represents a signed, fixed-length span of time represented
+    # as a count of seconds and fractions of seconds at nanosecond
+    # resolution. It is independent of any calendar and concepts like "day"
+    # or "month". It is related to Timestamp in that the difference between
+    # two Timestamp values is a Duration and it can be added or subtracted
+    # from a Timestamp. Range is approximately +-10,000 years.
+    #
+    # # Examples
+    #
+    # Example 1: Compute Duration from two Timestamps in pseudo code.
+    #
+    #     Timestamp start = ...;
+    #     Timestamp end = ...;
+    #     Duration duration = ...;
+    #
+    #     duration.seconds = end.seconds - start.seconds;
+    #     duration.nanos = end.nanos - start.nanos;
+    #
+    #     if (duration.seconds < 0 && duration.nanos > 0) {
+    #       duration.seconds += 1;
+    #       duration.nanos -= 1000000000;
+    #     } else if (duration.seconds > 0 && duration.nanos < 0) {
+    #       duration.seconds -= 1;
+    #       duration.nanos += 1000000000;
+    #     }
+    #
+    # Example 2: Compute Timestamp from Timestamp + Duration in pseudo code.
+    #
+    #     Timestamp start = ...;
+    #     Duration duration = ...;
+    #     Timestamp end = ...;
+    #
+    #     end.seconds = start.seconds + duration.seconds;
+    #     end.nanos = start.nanos + duration.nanos;
+    #
+    #     if (end.nanos < 0) {
+    #       end.seconds -= 1;
+    #       end.nanos += 1000000000;
+    #     } else if (end.nanos >= 1000000000) {
+    #       end.seconds += 1;
+    #       end.nanos -= 1000000000;
+    #     }
+    #
+    # Example 3: Compute Duration from datetime.timedelta in Python.
+    #
+    #     td = datetime.timedelta(days=3, minutes=10)
+    #     duration = Duration()
+    #     duration.FromTimedelta(td)
+    #
+    # # JSON Mapping
+    #
+    # In JSON format, the Duration type is encoded as a string rather than an
+    # object, where the string ends in the suffix "s" (indicating seconds) and
+    # is preceded by the number of seconds, with nanoseconds expressed as
+    # fractional seconds. For example, 3 seconds with 0 nanoseconds should be
+    # encoded in JSON format as "3s", while 3 seconds and 1 nanosecond should
+    # be expressed in JSON format as "3.000000001s", and 3 seconds and 1
+    # microsecond should be expressed in JSON format as "3.000001s".
+    # @!attribute [rw] seconds
+    #   @return [::Integer]
+    #     Signed seconds of the span of time. Must be from -315,576,000,000
+    #     to +315,576,000,000 inclusive. Note: these bounds are computed from:
+    #     60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
+    # @!attribute [rw] nanos
+    #   @return [::Integer]
+    #     Signed fractions of a second at nanosecond resolution of the span
+    #     of time. Durations less than one second are represented with a 0
+    #     `seconds` field and a positive or negative `nanos` field. For durations
+    #     of one second or more, a non-zero value for the `nanos` field must be
+    #     of the same sign as the `seconds` field. Must be from -999,999,999
+    #     to +999,999,999 inclusive.
+    class Duration
+      include ::Google::Protobuf::MessageExts
+      extend ::Google::Protobuf::MessageExts::ClassMethods
+    end
+  end
+end

data/proto_docs/google/protobuf/empty.rb

@@ -0,0 +1,34 @@
+# frozen_string_literal: true
+
+# Copyright 2025 Google LLC
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#     https://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+# Auto-generated by gapic-generator-ruby. DO NOT EDIT!
+
+
+module Google
+  module Protobuf
+    # A generic empty message that you can re-use to avoid defining duplicated
+    # empty messages in your APIs. A typical example is to use it as the request
+    # or the response type of an API method. For instance:
+    #
+    #     service Foo {
+    #       rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty);
+    #     }
+    class Empty
+      include ::Google::Protobuf::MessageExts
+      extend ::Google::Protobuf::MessageExts::ClassMethods
+    end
+  end
+end

data/proto_docs/google/protobuf/timestamp.rb

@@ -0,0 +1,127 @@
+# frozen_string_literal: true
+
+# Copyright 2025 Google LLC
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#     https://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+# Auto-generated by gapic-generator-ruby. DO NOT EDIT!
+
+
+module Google
+  module Protobuf
+    # A Timestamp represents a point in time independent of any time zone or local
+    # calendar, encoded as a count of seconds and fractions of seconds at
+    # nanosecond resolution. The count is relative to an epoch at UTC midnight on
+    # January 1, 1970, in the proleptic Gregorian calendar which extends the
+    # Gregorian calendar backwards to year one.
+    #
+    # All minutes are 60 seconds long. Leap seconds are "smeared" so that no leap
+    # second table is needed for interpretation, using a [24-hour linear
+    # smear](https://developers.google.com/time/smear).
+    #
+    # The range is from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z. By
+    # restricting to that range, we ensure that we can convert to and from [RFC
+    # 3339](https://www.ietf.org/rfc/rfc3339.txt) date strings.
+    #
+    # # Examples
+    #
+    # Example 1: Compute Timestamp from POSIX `time()`.
+    #
+    #     Timestamp timestamp;
+    #     timestamp.set_seconds(time(NULL));
+    #     timestamp.set_nanos(0);
+    #
+    # Example 2: Compute Timestamp from POSIX `gettimeofday()`.
+    #
+    #     struct timeval tv;
+    #     gettimeofday(&tv, NULL);
+    #
+    #     Timestamp timestamp;
+    #     timestamp.set_seconds(tv.tv_sec);
+    #     timestamp.set_nanos(tv.tv_usec * 1000);
+    #
+    # Example 3: Compute Timestamp from Win32 `GetSystemTimeAsFileTime()`.
+    #
+    #     FILETIME ft;
+    #     GetSystemTimeAsFileTime(&ft);
+    #     UINT64 ticks = (((UINT64)ft.dwHighDateTime) << 32) | ft.dwLowDateTime;
+    #
+    #     // A Windows tick is 100 nanoseconds. Windows epoch 1601-01-01T00:00:00Z
+    #     // is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z.
+    #     Timestamp timestamp;
+    #     timestamp.set_seconds((INT64) ((ticks / 10000000) - 11644473600LL));
+    #     timestamp.set_nanos((INT32) ((ticks % 10000000) * 100));
+    #
+    # Example 4: Compute Timestamp from Java `System.currentTimeMillis()`.
+    #
+    #     long millis = System.currentTimeMillis();
+    #
+    #     Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000)
+    #         .setNanos((int) ((millis % 1000) * 1000000)).build();
+    #
+    # Example 5: Compute Timestamp from Java `Instant.now()`.
+    #
+    #     Instant now = Instant.now();
+    #
+    #     Timestamp timestamp =
+    #         Timestamp.newBuilder().setSeconds(now.getEpochSecond())
+    #             .setNanos(now.getNano()).build();
+    #
+    # Example 6: Compute Timestamp from current time in Python.
+    #
+    #     timestamp = Timestamp()
+    #     timestamp.GetCurrentTime()
+    #
+    # # JSON Mapping
+    #
+    # In JSON format, the Timestamp type is encoded as a string in the
+    # [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) format. That is, the
+    # format is "\\{year}-\\{month}-\\{day}T\\{hour}:\\{min}:\\{sec}[.\\{frac_sec}]Z"
+    # where \\{year} is always expressed using four digits while \\{month}, \\{day},
+    # \\{hour}, \\{min}, and \\{sec} are zero-padded to two digits each. The fractional
+    # seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution),
+    # are optional. The "Z" suffix indicates the timezone ("UTC"); the timezone
+    # is required. A proto3 JSON serializer should always use UTC (as indicated by
+    # "Z") when printing the Timestamp type and a proto3 JSON parser should be
+    # able to accept both UTC and other timezones (as indicated by an offset).
+    #
+    # For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past
+    # 01:30 UTC on January 15, 2017.
+    #
+    # In JavaScript, one can convert a Date object to this format using the
+    # standard
+    # [toISOString()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString)
+    # method. In Python, a standard `datetime.datetime` object can be converted
+    # to this format using
+    # [`strftime`](https://docs.python.org/2/library/time.html#time.strftime) with
+    # the time format spec '%Y-%m-%dT%H:%M:%S.%fZ'. Likewise, in Java, one can use
+    # the Joda Time's [`ISODateTimeFormat.dateTime()`](
+    # http://joda-time.sourceforge.net/apidocs/org/joda/time/format/ISODateTimeFormat.html#dateTime()
+    # ) to obtain a formatter capable of generating timestamps in this format.
+    # @!attribute [rw] seconds
+    #   @return [::Integer]
+    #     Represents seconds of UTC time since Unix epoch
+    #     1970-01-01T00:00:00Z. Must be from 0001-01-01T00:00:00Z to
+    #     9999-12-31T23:59:59Z inclusive.
+    # @!attribute [rw] nanos
+    #   @return [::Integer]
+    #     Non-negative fractions of a second at nanosecond resolution. Negative
+    #     second values with fractions must still have non-negative nanos values
+    #     that count forward in time. Must be from 0 to 999,999,999
+    #     inclusive.
+    class Timestamp
+      include ::Google::Protobuf::MessageExts
+      extend ::Google::Protobuf::MessageExts::ClassMethods
+    end
+  end
+end

data/proto_docs/google/rpc/code.rb

@@ -0,0 +1,185 @@
+# frozen_string_literal: true
+
+# Copyright 2025 Google LLC
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#     https://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+# Auto-generated by gapic-generator-ruby. DO NOT EDIT!
+
+
+module Google
+  module Rpc
+    # The canonical error codes for gRPC APIs.
+    #
+    #
+    # Sometimes multiple error codes may apply.  Services should return
+    # the most specific error code that applies.  For example, prefer
+    # `OUT_OF_RANGE` over `FAILED_PRECONDITION` if both codes apply.
+    # Similarly prefer `NOT_FOUND` or `ALREADY_EXISTS` over `FAILED_PRECONDITION`.
+    module Code
+      # Not an error; returned on success.
+      #
+      # HTTP Mapping: 200 OK
+      OK = 0
+
+      # The operation was cancelled, typically by the caller.
+      #
+      # HTTP Mapping: 499 Client Closed Request
+      CANCELLED = 1
+
+      # Unknown error.  For example, this error may be returned when
+      # a `Status` value received from another address space belongs to
+      # an error space that is not known in this address space.  Also
+      # errors raised by APIs that do not return enough error information
+      # may be converted to this error.
+      #
+      # HTTP Mapping: 500 Internal Server Error
+      UNKNOWN = 2
+
+      # The client specified an invalid argument.  Note that this differs
+      # from `FAILED_PRECONDITION`.  `INVALID_ARGUMENT` indicates arguments
+      # that are problematic regardless of the state of the system
+      # (e.g., a malformed file name).
+      #
+      # HTTP Mapping: 400 Bad Request
+      INVALID_ARGUMENT = 3
+
+      # The deadline expired before the operation could complete. For operations
+      # that change the state of the system, this error may be returned
+      # even if the operation has completed successfully.  For example, a
+      # successful response from a server could have been delayed long
+      # enough for the deadline to expire.
+      #
+      # HTTP Mapping: 504 Gateway Timeout
+      DEADLINE_EXCEEDED = 4
+
+      # Some requested entity (e.g., file or directory) was not found.
+      #
+      # Note to server developers: if a request is denied for an entire class
+      # of users, such as gradual feature rollout or undocumented allowlist,
+      # `NOT_FOUND` may be used. If a request is denied for some users within
+      # a class of users, such as user-based access control, `PERMISSION_DENIED`
+      # must be used.
+      #
+      # HTTP Mapping: 404 Not Found
+      NOT_FOUND = 5
+
+      # The entity that a client attempted to create (e.g., file or directory)
+      # already exists.
+      #
+      # HTTP Mapping: 409 Conflict
+      ALREADY_EXISTS = 6
+
+      # The caller does not have permission to execute the specified
+      # operation. `PERMISSION_DENIED` must not be used for rejections
+      # caused by exhausting some resource (use `RESOURCE_EXHAUSTED`
+      # instead for those errors). `PERMISSION_DENIED` must not be
+      # used if the caller can not be identified (use `UNAUTHENTICATED`
+      # instead for those errors). This error code does not imply the
+      # request is valid or the requested entity exists or satisfies
+      # other pre-conditions.
+      #
+      # HTTP Mapping: 403 Forbidden
+      PERMISSION_DENIED = 7
+
+      # The request does not have valid authentication credentials for the
+      # operation.
+      #
+      # HTTP Mapping: 401 Unauthorized
+      UNAUTHENTICATED = 16
+
+      # Some resource has been exhausted, perhaps a per-user quota, or
+      # perhaps the entire file system is out of space.
+      #
+      # HTTP Mapping: 429 Too Many Requests
+      RESOURCE_EXHAUSTED = 8
+
+      # The operation was rejected because the system is not in a state
+      # required for the operation's execution.  For example, the directory
+      # to be deleted is non-empty, an rmdir operation is applied to
+      # a non-directory, etc.
+      #
+      # Service implementors can use the following guidelines to decide
+      # between `FAILED_PRECONDITION`, `ABORTED`, and `UNAVAILABLE`:
+      #  (a) Use `UNAVAILABLE` if the client can retry just the failing call.
+      #  (b) Use `ABORTED` if the client should retry at a higher level. For
+      #      example, when a client-specified test-and-set fails, indicating the
+      #      client should restart a read-modify-write sequence.
+      #  (c) Use `FAILED_PRECONDITION` if the client should not retry until
+      #      the system state has been explicitly fixed. For example, if an "rmdir"
+      #      fails because the directory is non-empty, `FAILED_PRECONDITION`
+      #      should be returned since the client should not retry unless
+      #      the files are deleted from the directory.
+      #
+      # HTTP Mapping: 400 Bad Request
+      FAILED_PRECONDITION = 9
+
+      # The operation was aborted, typically due to a concurrency issue such as
+      # a sequencer check failure or transaction abort.
+      #
+      # See the guidelines above for deciding between `FAILED_PRECONDITION`,
+      # `ABORTED`, and `UNAVAILABLE`.
+      #
+      # HTTP Mapping: 409 Conflict
+      ABORTED = 10
+
+      # The operation was attempted past the valid range.  E.g., seeking or
+      # reading past end-of-file.
+      #
+      # Unlike `INVALID_ARGUMENT`, this error indicates a problem that may
+      # be fixed if the system state changes. For example, a 32-bit file
+      # system will generate `INVALID_ARGUMENT` if asked to read at an
+      # offset that is not in the range [0,2^32-1], but it will generate
+      # `OUT_OF_RANGE` if asked to read from an offset past the current
+      # file size.
+      #
+      # There is a fair bit of overlap between `FAILED_PRECONDITION` and
+      # `OUT_OF_RANGE`.  We recommend using `OUT_OF_RANGE` (the more specific
+      # error) when it applies so that callers who are iterating through
+      # a space can easily look for an `OUT_OF_RANGE` error to detect when
+      # they are done.
+      #
+      # HTTP Mapping: 400 Bad Request
+      OUT_OF_RANGE = 11
+
+      # The operation is not implemented or is not supported/enabled in this
+      # service.
+      #
+      # HTTP Mapping: 501 Not Implemented
+      UNIMPLEMENTED = 12
+
+      # Internal errors.  This means that some invariants expected by the
+      # underlying system have been broken.  This error code is reserved
+      # for serious errors.
+      #
+      # HTTP Mapping: 500 Internal Server Error
+      INTERNAL = 13
+
+      # The service is currently unavailable.  This is most likely a
+      # transient condition, which can be corrected by retrying with
+      # a backoff. Note that it is not always safe to retry
+      # non-idempotent operations.
+      #
+      # See the guidelines above for deciding between `FAILED_PRECONDITION`,
+      # `ABORTED`, and `UNAVAILABLE`.
+      #
+      # HTTP Mapping: 503 Service Unavailable
+      UNAVAILABLE = 14
+
+      # Unrecoverable data loss or corruption.
+      #
+      # HTTP Mapping: 500 Internal Server Error
+      DATA_LOSS = 15
+    end
+  end
+end

data/proto_docs/google/rpc/status.rb

@@ -0,0 +1,48 @@
+# frozen_string_literal: true
+
+# Copyright 2025 Google LLC
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#     https://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+# Auto-generated by gapic-generator-ruby. DO NOT EDIT!
+
+
+module Google
+  module Rpc
+    # The `Status` type defines a logical error model that is suitable for
+    # different programming environments, including REST APIs and RPC APIs. It is
+    # used by [gRPC](https://github.com/grpc). Each `Status` message contains
+    # three pieces of data: error code, error message, and error details.
+    #
+    # You can find out more about this error model and how to work with it in the
+    # [API Design Guide](https://cloud.google.com/apis/design/errors).
+    # @!attribute [rw] code
+    #   @return [::Integer]
+    #     The status code, which should be an enum value of
+    #     {::Google::Rpc::Code google.rpc.Code}.
+    # @!attribute [rw] message
+    #   @return [::String]
+    #     A developer-facing error message, which should be in English. Any
+    #     user-facing error message should be localized and sent in the
+    #     {::Google::Rpc::Status#details google.rpc.Status.details} field, or localized
+    #     by the client.
+    # @!attribute [rw] details
+    #   @return [::Array<::Google::Protobuf::Any>]
+    #     A list of messages that carry the error details.  There is a common set of
+    #     message types for APIs to use.
+    class Status
+      include ::Google::Protobuf::MessageExts
+      extend ::Google::Protobuf::MessageExts::ClassMethods
+    end
+  end
+end

metadata

@@ -1,27 +1,113 @@
 --- !ruby/object:Gem::Specification
 name: google-cloud-storage_batch_operations-v1
 version: !ruby/object:Gem::Version
-  version: 0.a
+  version: 0.1.1
 platform: ruby
 authors:
 - Google LLC
 bindir: bin
 cert_chain: []
-date: 2025-04-16 00:00:00.000000000 Z
-dependencies: []
-description: Placeholder for the future Google-authored gem google-cloud-storage_batch_operations-v1.
-  This placeholder is being released on 2025-04-16 in order to reserve the name. The
-  final gem should be available shortly after that date. If it has not been released
-  in a timely manner, or if this placeholder interferes with your work, you can contact
-  the Google Ruby team by opening an issue in the GitHub repository https://github.com/googleapis/google-cloud-ruby.
+date: 2025-04-25 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: gapic-common
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 0.25.0
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: 2.a
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 0.25.0
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: 2.a
+- !ruby/object:Gem::Dependency
+  name: google-cloud-errors
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.0'
+- !ruby/object:Gem::Dependency
+  name: google-cloud-location
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0.7'
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: 2.a
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0.7'
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: 2.a
+description: google-cloud-storage_batch_operations-v1 is the official client library
+  for the Storage Batch Operations V1 API. Note that google-cloud-storage_batch_operations-v1
+  is a version-specific client library. For most uses, we recommend installing the
+  main client library google-cloud-storage_batch_operations instead. See the readme
+  for more details.
 email: googleapis-packages@google.com
 executables: []
 extensions: []
 extra_rdoc_files: []
 files:
+- ".yardopts"
+- AUTHENTICATION.md
 - LICENSE.md
 - README.md
+- lib/google-cloud-storage_batch_operations-v1.rb
+- lib/google/cloud/storage_batch_operations/v1.rb
+- lib/google/cloud/storage_batch_operations/v1/bindings_override.rb
+- lib/google/cloud/storage_batch_operations/v1/rest.rb
+- lib/google/cloud/storage_batch_operations/v1/storage_batch_operations.rb
+- lib/google/cloud/storage_batch_operations/v1/storage_batch_operations/client.rb
+- lib/google/cloud/storage_batch_operations/v1/storage_batch_operations/credentials.rb
+- lib/google/cloud/storage_batch_operations/v1/storage_batch_operations/operations.rb
+- lib/google/cloud/storage_batch_operations/v1/storage_batch_operations/paths.rb
+- lib/google/cloud/storage_batch_operations/v1/storage_batch_operations/rest.rb
+- lib/google/cloud/storage_batch_operations/v1/storage_batch_operations/rest/client.rb
+- lib/google/cloud/storage_batch_operations/v1/storage_batch_operations/rest/operations.rb
+- lib/google/cloud/storage_batch_operations/v1/storage_batch_operations/rest/service_stub.rb
 - lib/google/cloud/storage_batch_operations/v1/version.rb
+- lib/google/cloud/storagebatchoperations/v1/storage_batch_operations_pb.rb
+- lib/google/cloud/storagebatchoperations/v1/storage_batch_operations_services_pb.rb
+- lib/google/cloud/storagebatchoperations/v1/storage_batch_operations_types_pb.rb
+- proto_docs/README.md
+- proto_docs/google/api/client.rb
+- proto_docs/google/api/field_behavior.rb
+- proto_docs/google/api/launch_stage.rb
+- proto_docs/google/api/resource.rb
+- proto_docs/google/cloud/storagebatchoperations/v1/storage_batch_operations.rb
+- proto_docs/google/cloud/storagebatchoperations/v1/storage_batch_operations_types.rb
+- proto_docs/google/longrunning/operations.rb
+- proto_docs/google/protobuf/any.rb
+- proto_docs/google/protobuf/duration.rb
+- proto_docs/google/protobuf/empty.rb
+- proto_docs/google/protobuf/timestamp.rb
+- proto_docs/google/rpc/code.rb
+- proto_docs/google/rpc/status.rb
 homepage: https://github.com/googleapis/google-cloud-ruby
 licenses:
 - Apache-2.0
@@ -42,5 +128,5 @@ required_rubygems_version: !ruby/object:Gem::Requirement
 requirements: []
 rubygems_version: 3.6.5
 specification_version: 4
-summary: Placeholder for the future Google-authored gem google-cloud-storage_batch_operations-v1
+summary: API Client library for the Storage Batch Operations V1 API
 test_files: []