feat(osconfig): update the API

#### osconfig:v1beta

The following keys were added:
- schemas.PatchConfig.properties.skipUnpatchableVms.description
- schemas.PatchConfig.properties.skipUnpatchableVms.type
- schemas.PatchJobInstanceDetailsSummary.properties.skippedInstanceCount.description
- schemas.PatchJobInstanceDetailsSummary.properties.skippedInstanceCount.format
- schemas.PatchJobInstanceDetailsSummary.properties.skippedInstanceCount.type

The following keys were changed:
- schemas.PatchJob.properties.state.enum
- schemas.PatchJob.properties.state.enumDescriptions
- schemas.PatchJobInstanceDetails.properties.state.enum
- schemas.PatchJobInstanceDetails.properties.state.enumDescriptions

#### osconfig:v1

The following keys were added:
- schemas.PatchConfig.properties.skipUnpatchableVms.description
- schemas.PatchConfig.properties.skipUnpatchableVms.type
- schemas.PatchJobInstanceDetailsSummary.properties.skippedInstanceCount.description
- schemas.PatchJobInstanceDetailsSummary.properties.skippedInstanceCount.format
- schemas.PatchJobInstanceDetailsSummary.properties.skippedInstanceCount.type

The following keys were changed:
- schemas.PatchJob.properties.state.enum
- schemas.PatchJob.properties.state.enumDescriptions
- schemas.PatchJobInstanceDetails.properties.state.enum
- schemas.PatchJobInstanceDetails.properties.state.enumDescriptions

Author: yoshi-automation

discovery/osconfig-v1.json

@@ -1083,7 +1083,7 @@
       }
     }
   },
-  "revision": "20250727",
+  "revision": "20251030",
   "rootUrl": "https://osconfig.googleapis.com/",
   "schemas": {
     "AptSettings": {
@@ -3061,6 +3061,10 @@
           ],
           "type": "string"
         },
+        "skipUnpatchableVms": {
+          "description": "Optional. Enables enhanced reporting for the patch job: 1. Allows the patch job to skip unpatchable instances, reporting them as SKIPPED. An instance can be unpatchable for two reasons: a. The instance runs Container-Optimized OS (COS), which cannot be patched. b. The patch job's configuration prohibits patching on Managed Instance Groups (MIGs) through the PatchConfig.migInstancesAllowed field, and the instance is part of one. 2. The system reports the patch job as SUCCEEDED if it completes without errors, regardless of whether any instances were SKIPPED. 3. The system reports the patch job as COMPLETED_WITH_INACTIVE_VMS if it completes without errors, but some instances were INACTIVE and therefore not patched.",
+          "type": "boolean"
+        },
         "windowsUpdate": {
           "$ref": "WindowsUpdateSettings",
           "description": "Windows update settings. Use this override the default windows patch rules."
@@ -3270,6 +3274,7 @@
             "INSTANCE_LOOKUP",
             "PATCHING",
             "SUCCEEDED",
+            "COMPLETED_WITH_INACTIVE_VMS",
             "COMPLETED_WITH_ERRORS",
             "CANCELED",
             "TIMED_OUT"
@@ -3280,6 +3285,7 @@
             "The patch job is looking up instances to run the patch on.",
             "Instances are being patched.",
             "Patch job completed successfully.",
+            "The patch job completed without errors, but some instances were inactive and therefore not patched.",
             "Patch job completed but there were errors.",
             "The patch job was canceled.",
             "The patch job timed out."
@@ -3333,7 +3339,8 @@
             "TIMED_OUT",
             "RUNNING_PRE_PATCH_STEP",
             "RUNNING_POST_PATCH_STEP",
-            "NO_AGENT_DETECTED"
+            "NO_AGENT_DETECTED",
+            "SKIPPED"
           ],
           "enumDescriptions": [
             "Unspecified.",
@@ -3351,7 +3358,8 @@
             "The instance exceeded the time out while applying the patch.",
             "The instance is running the pre-patch step.",
             "The instance is running the post-patch step.",
-            "The service could not detect the presence of the agent. Check to ensure that the agent is installed, running, and able to communicate with the service."
+            "The service could not detect the presence of the agent. Check to ensure that the agent is installed, running, and able to communicate with the service.",
+            "The instance was skipped during patching due to one of two reasons: 1. The instance runs Container-Optimized OS (COS), which cannot be patched. 2. The patch job's configuration prohibits patching on Managed Instance Groups (MIGs), and the instance is part of one."
           ],
           "type": "string"
         }
@@ -3417,6 +3425,11 @@
           "format": "int64",
           "type": "string"
         },
+        "skippedInstanceCount": {
+          "description": "Number of instances that were skipped during patching.",
+          "format": "int64",
+          "type": "string"
+        },
         "startedInstanceCount": {
           "description": "Number of instances that have started.",
           "format": "int64",

discovery/osconfig-v1beta.json

@@ -689,7 +689,7 @@
       }
     }
   },
-  "revision": "20250511",
+  "revision": "20251030",
   "rootUrl": "https://osconfig.googleapis.com/",
   "schemas": {
     "AptRepository": {
@@ -1565,6 +1565,10 @@
           ],
           "type": "string"
         },
+        "skipUnpatchableVms": {
+          "description": "Optional. Enables enhanced reporting for the patch job: 1. Allows the patch job to skip unpatchable instances, reporting them as SKIPPED. An instance can be unpatchable for two reasons: a. The instance runs Container-Optimized OS (COS), which cannot be patched. b. The patch job's configuration prohibits patching on Managed Instance Groups (MIGs) through the PatchConfig.migInstancesAllowed field, and the instance is part of one. 2. The system reports the patch job as SUCCEEDED if it completes without errors, regardless of whether any instances were SKIPPED. 3. The system reports the patch job as COMPLETED_WITH_INACTIVE_VMS if it completes without errors, but some instances were INACTIVE and therefore not patched.",
+          "type": "boolean"
+        },
         "windowsUpdate": {
           "$ref": "WindowsUpdateSettings",
           "description": "Windows update settings. Use this override the default windows patch rules."
@@ -1774,6 +1778,7 @@
             "INSTANCE_LOOKUP",
             "PATCHING",
             "SUCCEEDED",
+            "COMPLETED_WITH_INACTIVE_VMS",
             "COMPLETED_WITH_ERRORS",
             "CANCELED",
             "TIMED_OUT"
@@ -1784,6 +1789,7 @@
             "The patch job is looking up instances to run the patch on.",
             "Instances are being patched.",
             "Patch job completed successfully.",
+            "The patch job completed without errors, but some instances were inactive and therefore not patched.",
             "Patch job completed but there were errors.",
             "The patch job was canceled.",
             "The patch job timed out."
@@ -1837,7 +1843,8 @@
             "TIMED_OUT",
             "RUNNING_PRE_PATCH_STEP",
             "RUNNING_POST_PATCH_STEP",
-            "NO_AGENT_DETECTED"
+            "NO_AGENT_DETECTED",
+            "SKIPPED"
           ],
           "enumDescriptions": [
             "Unspecified.",
@@ -1855,7 +1862,8 @@
             "The instance exceeded the time out while applying the patch.",
             "The instance is running the pre-patch step.",
             "The instance is running the post-patch step.",
-            "The service could not detect the presence of the agent. Check to ensure that the agent is installed, running, and able to communicate with the service."
+            "The service could not detect the presence of the agent. Check to ensure that the agent is installed, running, and able to communicate with the service.",
+            "The instance was skipped during patching due to one of two reasons: 1. The instance runs Container-Optimized OS (COS), which cannot be patched. 2. The patch job's configuration prohibits patching on Managed Instance Groups (MIGs), and the instance is part of one."
           ],
           "type": "string"
         }
@@ -1921,6 +1929,11 @@
           "format": "int64",
           "type": "string"
         },
+        "skippedInstanceCount": {
+          "description": "Number of instances that were skipped during patching.",
+          "format": "int64",
+          "type": "string"
+        },
         "startedInstanceCount": {
           "description": "Number of instances that have started.",
           "format": "int64",

src/apis/osconfig/v1.ts

@@ -1502,6 +1502,10 @@ export namespace osconfig_v1 {
      * Post-patch reboot settings.
      */
     rebootConfig?: string | null;
+    /**
+     * Optional. Enables enhanced reporting for the patch job: 1. Allows the patch job to skip unpatchable instances, reporting them as SKIPPED. An instance can be unpatchable for two reasons: a. The instance runs Container-Optimized OS (COS), which cannot be patched. b. The patch job's configuration prohibits patching on Managed Instance Groups (MIGs) through the PatchConfig.migInstancesAllowed field, and the instance is part of one. 2. The system reports the patch job as SUCCEEDED if it completes without errors, regardless of whether any instances were SKIPPED. 3. The system reports the patch job as COMPLETED_WITH_INACTIVE_VMS if it completes without errors, but some instances were INACTIVE and therefore not patched.
+     */
+    skipUnpatchableVms?: boolean | null;
     /**
      * Windows update settings. Use this override the default windows patch rules.
      */
@@ -1740,6 +1744,10 @@ export namespace osconfig_v1 {
      * Number of instances rebooting.
      */
     rebootingInstanceCount?: string | null;
+    /**
+     * Number of instances that were skipped during patching.
+     */
+    skippedInstanceCount?: string | null;
     /**
      * Number of instances that have started.
      */

src/apis/osconfig/v1beta.ts

@@ -713,6 +713,10 @@ export namespace osconfig_v1beta {
      * Post-patch reboot settings.
      */
     rebootConfig?: string | null;
+    /**
+     * Optional. Enables enhanced reporting for the patch job: 1. Allows the patch job to skip unpatchable instances, reporting them as SKIPPED. An instance can be unpatchable for two reasons: a. The instance runs Container-Optimized OS (COS), which cannot be patched. b. The patch job's configuration prohibits patching on Managed Instance Groups (MIGs) through the PatchConfig.migInstancesAllowed field, and the instance is part of one. 2. The system reports the patch job as SUCCEEDED if it completes without errors, regardless of whether any instances were SKIPPED. 3. The system reports the patch job as COMPLETED_WITH_INACTIVE_VMS if it completes without errors, but some instances were INACTIVE and therefore not patched.
+     */
+    skipUnpatchableVms?: boolean | null;
     /**
      * Windows update settings. Use this override the default windows patch rules.
      */
@@ -951,6 +955,10 @@ export namespace osconfig_v1beta {
      * Number of instances rebooting.
      */
     rebootingInstanceCount?: string | null;
+    /**
+     * Number of instances that were skipped during patching.
+     */
+    skippedInstanceCount?: string | null;
     /**
      * Number of instances that have started.
      */