feat: add a CloudLoggingOption and use_generic_task_monitored_resourc…

…e fields for users to opt out new batch monitored resource in cloud logging

docs: update comment for AllocationPolicy.network

PiperOrigin-RevId: 584365225

google/cloud/batch/v1/job.proto

@@ -91,6 +91,10 @@ message Job {
 // LogsPolicy describes how outputs from a Job's Tasks (stdout/stderr) will be
 // preserved.
 message LogsPolicy {
+  // CloudLoggingOption contains additional settings for cloud logging generated
+  // by Batch job.
+  message CloudLoggingOption {}
+
   // The destination (if any) for logs.
   enum Destination {
     // Logs are not preserved.
@@ -110,6 +114,11 @@ message LogsPolicy {
   // local file path on the VM, or under the mount point of a Persistent Disk or
   // Filestore, or a Cloud Storage path.
   string logs_path = 2;
+
+  // Optional. Additional settings for Cloud Logging. It will only take effect
+  // when the destination of LogsPolicy is set to CLOUD_LOGGING.
+  CloudLoggingOption cloud_logging_option = 3
+      [(google.api.field_behavior) = OPTIONAL];
 }
 
 // Job status.
@@ -507,6 +516,10 @@ message AllocationPolicy {
   map<string, string> labels = 6;
 
   // The network policy.
+  //
+  // If you define an instance template in the InstancePolicyOrTemplate field,
+  // Batch will use the network settings in the instance template instead of
+  // this field.
   NetworkPolicy network = 7;
 
   // The placement policy.