Blake Li

I agree it's not straightforward to set up API Keys at this moment, and it is not documented either. I created a separate issue https://github.com/googleapis/google-cloud-java/issues/10921 to track the documentation effort.

There were errors in sdk-platform-java's [CI](https://github.com/googleapis/sdk-platform-java/actions/runs/11828213668/job/32958236632) ``` (00:37:16) ERROR: /home/runner/.cache/bazel/_bazel_runner/cf5fb8c2c66b8a944ea6af7c9b248db5/external/maven/BUILD:41:11: no such target '@io_grpc_grpc_java//s2a:s2a': target 's2a' not declared in package 's2a' defined by /home/runner/.cache/bazel/_bazel_runner/cf5fb8c2c66b8a944ea6af7c9b248db5/external/io_grpc_grpc_java/s2a/BUILD.bazel (Tip: use `query "@io_grpc_grpc_java//s2a:*"` to see...

Hi @lkleeven, thanks for reporting this! I think your request is reasonable, but we may not expose these two settings at this moment. Because 1. Channel resizing is expensive and...

>if we add another client, won't we be also creating those channels which are expensive? Yes creating channels are expensive, and it is unavoidable either we resize channels in the...

Closing due to inactivity. @Alarm1673 Please reopen if you are still running into this issue.

The [proto changes](https://github.com/googleapis/googleapis/pull/903) in googleapis is not merged yet. The Java client library should be auto-generated and released in two weeks after the proto changes are merged.

I can see changes related to [SEV_SNP](https://github.com/googleapis/google-cloud-java/blame/885e8252a0aad01a47ac2161f7a1183b450d144b/java-compute/proto-google-cloud-compute-v1/src/main/java/com/google/cloud/compute/v1/ConfidentialInstanceConfig.java#L169) are already on main branch, and we just released it today. Can you double check [java-compute](https://github.com/googleapis/google-cloud-java/tree/main/java-compute) already has all the latest changes?

This is a quality of life testing improvement, does not affect any functionality. Downgrade to P3 and change the type to cleanup.

Do you expect it to be always enabled in java-spanner? Or enabled on-demand?

Thanks Burke! How did you notice this issue?