feat(gkeonprem): update the API

#### gkeonprem:v1 The following keys were added: - schemas.VmwareAdminCluster.properties.preparedSecrets.$ref - schemas.VmwareAdminCluster.properties.preparedSecrets.description - schemas.VmwareAdminPreparedSecretsConfig.description - schemas.VmwareAdminPreparedSecretsConfig.id - schemas.VmwareAdminPreparedSecretsConfig.properties.enabled.description - schemas.VmwareAdminPreparedSecretsConfig.properties.enabled.type - schemas.VmwareAdminPreparedSecretsConfig.type The following keys were changed: - schemas.BareMetalAdminCluster.description - schemas.BareMetalCluster.description
googleapis · Oct 19, 2023 · 79b5c9c · 79b5c9c
1 parent 3b2cd4d
commit 79b5c9c
Show file tree

Hide file tree

Showing 2 changed files with 33 additions and 5 deletions.
diff --git a/discovery/gkeonprem-v1.json b/discovery/gkeonprem-v1.json
@@ -2996,7 +2996,7 @@
       }
     }
   },
-  "revision": "20230925",
+  "revision": "20231004",
   "rootUrl": "https://gkeonprem.googleapis.com/",
   "schemas": {
     "Authorization": {
@@ -3029,7 +3029,7 @@
       "type": "object"
     },
     "BareMetalAdminCluster": {
-      "description": "## Resource that represents a bare metal admin cluster.",
+      "description": "Resource that represents a bare metal admin cluster. LINT.IfChange",
       "id": "BareMetalAdminCluster",
       "properties": {
         "annotations": {
@@ -3532,7 +3532,7 @@
       "type": "object"
     },
     "BareMetalCluster": {
-      "description": "Resource that represents a bare metal user cluster.",
+      "description": "Resource that represents a bare metal user cluster. LINT.IfChange",
       "id": "BareMetalCluster",
       "properties": {
         "adminClusterMembership": {
@@ -5503,6 +5503,10 @@
           "$ref": "VmwarePlatformConfig",
           "description": "The VMware platform configuration."
         },
+        "preparedSecrets": {
+          "$ref": "VmwareAdminPreparedSecretsConfig",
+          "description": "The VMware admin cluster prepared secrets configuration."
+        },
         "reconciling": {
           "description": "Output only. If set, there are currently changes in flight to the VMware admin cluster.",
           "readOnly": true,
@@ -5712,6 +5716,17 @@
       },
       "type": "object"
     },
+    "VmwareAdminPreparedSecretsConfig": {
+      "description": "VmwareAdminPreparedSecretsConfig represents configuration for admin cluster prepared secrets.",
+      "id": "VmwareAdminPreparedSecretsConfig",
+      "properties": {
+        "enabled": {
+          "description": "Whether prepared secrets is enabled.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
     "VmwareAdminSeesawConfig": {
       "description": "VmwareSeesawConfig represents configuration parameters for an already existing Seesaw load balancer. IMPORTANT: Please note that the Anthos On-Prem API will not generate or update Seesaw configurations it can only bind a pre-existing configuration to a new user cluster. IMPORTANT: When attempting to create a user cluster with a pre-existing Seesaw load balancer you will need to follow some preparation steps before calling the 'CreateVmwareCluster' API method. First you will need to create the user cluster's namespace via kubectl. The namespace will need to use the following naming convention : -gke-onprem-mgmt or -gke-onprem-mgmt depending on whether you used the 'VmwareCluster.local_name' to disambiguate collisions; for more context see the documentation of 'VmwareCluster.local_name'. Once the namespace is created you will need to create a secret resource via kubectl. This secret will contain copies of your Seesaw credentials. The Secret must be called 'user-cluster-creds' and contain Seesaw's SSH and Cert credentials. The credentials must be keyed with the following names: 'seesaw-ssh-private-key', 'seesaw-ssh-public-key', 'seesaw-ssh-ca-key', 'seesaw-ssh-ca-cert'.",
       "id": "VmwareAdminSeesawConfig",

diff --git a/src/apis/gkeonprem/v1.ts b/src/apis/gkeonprem/v1.ts
@@ -147,7 +147,7 @@ export namespace gkeonprem_v1 {
     value?: string | null;
   }
   /**
-   * ## Resource that represents a bare metal admin cluster.
+   * Resource that represents a bare metal admin cluster. LINT.IfChange
    */
   export interface Schema$BareMetalAdminCluster {
     /**
@@ -531,7 +531,7 @@ export namespace gkeonprem_v1 {
     ipAddress?: string | null;
   }
   /**
-   * Resource that represents a bare metal user cluster.
+   * Resource that represents a bare metal user cluster. LINT.IfChange
    */
   export interface Schema$BareMetalCluster {
     /**
@@ -1917,6 +1917,10 @@ export namespace gkeonprem_v1 {
      * The VMware platform configuration.
      */
     platformConfig?: Schema$VmwarePlatformConfig;
+    /**
+     * The VMware admin cluster prepared secrets configuration.
+     */
+    preparedSecrets?: Schema$VmwareAdminPreparedSecretsConfig;
     /**
      * Output only. If set, there are currently changes in flight to the VMware admin cluster.
      */
@@ -2069,6 +2073,15 @@ export namespace gkeonprem_v1 {
      */
     vcenterNetwork?: string | null;
   }
+  /**
+   * VmwareAdminPreparedSecretsConfig represents configuration for admin cluster prepared secrets.
+   */
+  export interface Schema$VmwareAdminPreparedSecretsConfig {
+    /**
+     * Whether prepared secrets is enabled.
+     */
+    enabled?: boolean | null;
+  }
   /**
    * VmwareSeesawConfig represents configuration parameters for an already existing Seesaw load balancer. IMPORTANT: Please note that the Anthos On-Prem API will not generate or update Seesaw configurations it can only bind a pre-existing configuration to a new user cluster. IMPORTANT: When attempting to create a user cluster with a pre-existing Seesaw load balancer you will need to follow some preparation steps before calling the 'CreateVmwareCluster' API method. First you will need to create the user cluster's namespace via kubectl. The namespace will need to use the following naming convention : -gke-onprem-mgmt or -gke-onprem-mgmt depending on whether you used the 'VmwareCluster.local_name' to disambiguate collisions; for more context see the documentation of 'VmwareCluster.local_name'. Once the namespace is created you will need to create a secret resource via kubectl. This secret will contain copies of your Seesaw credentials. The Secret must be called 'user-cluster-creds' and contain Seesaw's SSH and Cert credentials. The credentials must be keyed with the following names: 'seesaw-ssh-private-key', 'seesaw-ssh-public-key', 'seesaw-ssh-ca-key', 'seesaw-ssh-ca-cert'.
    */