Bump google-cloud-storage from 1.113.1 to 2.15.1 in /plugins/repository-gcs

[dependabot]

Bumps google-cloud-storage from 1.113.1 to 2.15.1.

Release notes

Sourced from google-cloud-storage's releases.

v2.15.1

2.15.1 (2022-11-17)

Bug Fixes

• Disable REGAPIC transport in storage v2 (#1762) (13d630e)
• Update GrpcStorageImpl#get(BlobId) to return null on 404 (#1772) (8c59c64)

Documentation

• Annotate all Option factory methods with their Nullability bounds (#1775) (3b8d137)

v2.15.0

2.15.0 (2022-11-07)

Features

• Add Autoclass support and sample (#1697) (82aacd7)
• Update retries for Notifications (#1734) (0fb2f18)

Dependencies

• Update dependency com.google.cloud:google-cloud-shared-dependencies to v3.0.6 (#1761) (803a90b)
• Update dependency net.jqwik:jqwik to v1.7.1 (#1758) (140e909)
• Update dependency org.graalvm.buildtools:native-maven-plugin to v0.9.17 (#1759) (7e3175a)

v2.14.0

2.14.0 (2022-10-26)

Google Cloud Storage gRPC API Preview

The first release of google-cloud-storage with support for a subset of the Google Cloud Storage gRPC API which is in private preview. The most common operations have all been implemented and are available for experimentation.

Given not all public api surface of google-cloud-storage classes are supported for gRPC a new annotation @TransportCompatibility has been added to various classes, methods and fields/enum values to signal where that thing can be expected to work. As we implement more of the operations these annotations will be updated.

All new gRPC related APIs are annotated with @BetaApi to denote they are in preview and the possibility of breaking change is present. At this time, opting to use any of the gRPC transport mode means you are okay with the possibility of a breaking change happening. When the APIs are out of preview, we will remove the @BetaApi annotation to signal they are now considered stable and will not break outside a major version.

NOTICE: Using the gRPC transport is exclusive. Any operations which have not yet been implemented for gRPC will result in a runtime error. For those operations which are not yet implemented, please continue to use the existing HTTP transport.

Special thanks (in alphabetical order) to @​BenWhitehead, @​frankyn, @​jesselovelace and @​sydney-munro for their hard work on this effort.

Notable Improvements

1. For all gRPC media related operations (upload/download) we are now more resource courteous then the corresponding HTTP counterpart. Buffers are fixed to their specified size (can't arbitrarily grow without bounds), are allocated lazily and only if necessary.

   1. Investigation into the possibility of backporting these improvements to the HTTP counterparts is ongoing

2. Preview support for Accessing GCS via gRPC

   1. Set the environment variable GOOGLE_CLOUD_ENABLE_DIRECT_PATH_XDS=true, then run your program.

... (truncated)

Changelog

Sourced from google-cloud-storage's changelog.

2.15.1 (2022-11-17)

Bug Fixes

• Disable REGAPIC transport in storage v2 (#1762) (13d630e)
• Update GrpcStorageImpl#get(BlobId) to return null on 404 (#1772) (8c59c64)

Documentation

• Annotate all Option factory methods with their Nullability bounds (#1775) (3b8d137)

2.15.0 (2022-11-07)

Features

• Add Autoclass support and sample (#1697) (82aacd7)
• Update retries for Notifications (#1734) (0fb2f18)

Dependencies

• Update dependency com.google.cloud:google-cloud-shared-dependencies to v3.0.6 (#1761) (803a90b)
• Update dependency net.jqwik:jqwik to v1.7.1 (#1758) (140e909)
• Update dependency org.graalvm.buildtools:native-maven-plugin to v0.9.17 (#1759) (7e3175a)

2.14.0 (2022-10-26)

Google Cloud Storage gRPC API Preview

The first release of google-cloud-storage with support for a subset of the Google Cloud Storage gRPC API which is in private preview. The most common operations have all been implemented and are available for experimentation.

Given not all public api surface of google-cloud-storage classes are supported for gRPC a new annotation @TransportCompatibility has been added to various classes, methods and fields/enum values to signal where that thing can be expected to work. As we implement more of the operations these annotations will be updated.

All new gRPC related APIs are annotated with @BetaApi to denote they are in preview and the possibility of breaking change is present. At this time, opting to use any of the gRPC transport mode means you are okay with the possibility of a breaking change happening. When the APIs are out of preview, we will remove the @BetaApi annotation to signal they are now considered stable and will not break outside a major version.

NOTICE: Using the gRPC transport is exclusive. Any operations which have not yet been implemented for gRPC will result in a runtime error. For those operations which are not yet implemented, please continue to use the existing HTTP transport.

Special thanks (in alphabetical order) to @​BenWhitehead, @​frankyn, @​jesselovelace and @​sydney-munro for their hard work on this effort.

Notable Improvements

1. For all gRPC media related operations (upload/download) we are now more resource courteous then the corresponding HTTP counterpart. Buffers are fixed to their specified size (can't arbitrarily grow without bounds), are allocated lazily and only if necessary.

   1. Investigation into the possibility of backporting these improvements to the HTTP counterparts is ongoing

2. Preview support for Accessing GCS via gRPC

   1. Set the environment variable GOOGLE_CLOUD_ENABLE_DIRECT_PATH_XDS=true, then run your program.
   2. When configuring your StorageOptions mimic the following:

       StorageOptions.grpc()
      

... (truncated)

Commits

• bfd48a1 chore(main): release 2.15.1 (#1765)
• 3b8d137 docs: annotate all Option factory methods with their Nullability bounds (#1775)
• ba49f9d test(deps): update kms.version to v0.100.0 (#1774)
• 8c59c64 fix: update GrpcStorageImpl#get(BlobId) to return null on 404 (#1772)
• 2770a38 test(deps): update dependency org.mockito:mockito-core to v4.9.0 (#1773)
• 45b2b38 chore: use gcp-docuploader 0.6.3 (#1708) (#1769)
• e0efa85 test(deps): update dependency com.google.cloud:google-cloud-pubsub to v1.120....
• feb9f06 test(deps): update dependency com.google.api.grpc:proto-google-cloud-pubsub-v...
• b05ee42 test(deps): update testbench version to v0.32.0 (#1768)
• 8ea8131 chore: update google-auth to 2.14.1 (#1703) (#1767)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/7382/
• CommitID: fe11842
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure a flaky test unrelated to your change?

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/7381/
• CommitID: 21cc06a
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure a flaky test unrelated to your change?

[dependabot]

Superseded by #5521.