feat(batch-v1): Support for blocking project-level SSH keys (#27288)

google-cloud-batch-v1/proto_docs/google/cloud/batch/v1/job.rb

@@ -532,6 +532,25 @@ class InstancePolicy
           #   @return [::Boolean]
           #     Optional. Set this field true if you want Batch to install Ops Agent on
           #     your behalf. Default is false.
+          # @!attribute [rw] block_project_ssh_keys
+          #   @return [::Boolean]
+          #     Optional. Set this field to `true` if you want Batch to block
+          #     project-level SSH keys from accessing this job's VMs.  Alternatively, you
+          #     can configure the job to specify a VM instance template that blocks
+          #     project-level SSH keys. In either case, Batch blocks project-level SSH
+          #     keys while creating the VMs for this job.
+          #
+          #     Batch allows project-level SSH keys for a job's VMs only if all
+          #     the following are true:
+          #
+          #     + This field is undefined or set to `false`.
+          #     + The job's VM instance template (if any) doesn't block project-level
+          #       SSH keys.
+          #
+          #     Notably, you can override this behavior by manually updating a VM to
+          #     block or allow project-level SSH keys. For more information about
+          #     blocking project-level SSH keys, see the Compute Engine documentation:
+          #     https://cloud.google.com/compute/docs/connect/restrict-ssh-keys#block-keys
           class InstancePolicyOrTemplate
             include ::Google::Protobuf::MessageExts
             extend ::Google::Protobuf::MessageExts::ClassMethods