chore: Update gcloud CLI options (#2578)

Co-authored-by: thomhurst <9139608+thomhurst@users.noreply.github.com>

Author: thomhurst

src/ModularPipelines.Google/AssemblyInfo.Generated.cs

@@ -6,4 +6,4 @@
 using System.Reflection;
 
 [assembly: AssemblyMetadata("ModularPipelines.OptionsGenerator.Tool", "gcloud")]
-[assembly: AssemblyMetadata("ModularPipelines.OptionsGenerator.GeneratedAt", "2026-04-26T03:45:21.8834943Z")]
+[assembly: AssemblyMetadata("ModularPipelines.OptionsGenerator.GeneratedAt", "2026-05-03T03:56:05.4249838Z")]

src/ModularPipelines.Google/Enums/GcloudConcurrencyMode.Generated.cs

@@ -0,0 +1,22 @@
+// <auto-generated>
+// This file was generated by ModularPipelines.OptionsGenerator.
+// Do not edit this file manually.
+// </auto-generated>
+
+using System.CodeDom.Compiler;
+using System.ComponentModel;
+
+namespace ModularPipelines.Google.Enums;
+
+/// <summary>
+/// Allowed values for --concurrencymode.
+/// </summary>
+[GeneratedCode("ModularPipelines.OptionsGenerator", "")]
+public enum GcloudConcurrencyMode
+{
+    [Description("optimistic")]
+    Optimistic,
+
+    [Description("pessimistic")]
+    Pessimistic
+}

src/ModularPipelines.Google/Extensions/GcloudExtensions.Generated.cs

@@ -156,6 +156,7 @@ public static IServiceCollection RegisterGcloudContext(this IServiceCollection s
         services.TryAddScoped<GcloudVmware>();
         services.TryAddScoped<GcloudWorkbench>();
         services.TryAddScoped<GcloudWorkflows>();
+        services.TryAddScoped<GcloudWorkloadidentity>();
         services.TryAddScoped<GcloudWorkspaceaddons>();
         services.TryAddScoped<GcloudWorkstations>();
         return services;

src/ModularPipelines.Google/Options/GcloudBeyondcorpSecurityGatewaysCreateOptions.Generated.cs

@@ -39,12 +39,6 @@ public record GcloudBeyondcorpSecurityGatewaysCreateOptions : GcloudOptions
     [CliOption("--hubs", Format = OptionFormat.EqualsSeparated, AllowMultiple = true)]
     public IEnumerable<string>? Hubs { get; set; }
 
-    /// <summary>
-    /// Configuration for Cloud Logging.     Shorthand Example:       --logging=     JSON Example:       --logging={}     File Example:       --logging=path_to_file.(yaml|json)
-    /// </summary>
-    [CliOption("--logging", Format = OptionFormat.EqualsSeparated, AllowMultiple = true)]
-    public IEnumerable<string>? Logging { get; set; }
-
     /// <summary>
     /// An optional request ID to identify requests. Specify a unique request     ID so that if you must retry your request, the server will know to     ignore the request if it has already been completed. The server will     guarantee that for at least 60 minutes since the first request.    The configuration for the proxy.
     /// </summary>

src/ModularPipelines.Google/Options/GcloudBeyondcorpSecurityGatewaysUpdateOptions.Generated.cs

@@ -34,7 +34,7 @@ public record GcloudBeyondcorpSecurityGatewaysUpdateOptions : GcloudOptions
     public string? DisplayName { get; set; }
 
     /// <summary>
-    /// An optional request ID to identify requests. Specify a unique request     ID so that if you must retry your request, the server will know to     ignore the request if it has already been completed. The server will     guarantee that for at least 60 minutes after the first request.     For example, consider a situation where you make an initial request and     the request timed out. If you make the request again with the same     request ID, the server can check if original operation with the same     request ID was received, and if so, will ignore the second request.     This prevents clients from accidentally creating duplicate commitments.     The request ID must be a valid UUID with the exception that zero UUID     is not supported (00000000-0000-0000-0000-000000000000).    Set the value of   googleCloudBeyondcorpSecuritygatewaysV1SecurityGateway.logging by using   flag [logging] or flags [].    At most one of these can be specified:      Configuration for Cloud Logging.      --clear-logging       Set googleCloudBeyondcorpSecuritygatewaysV1SecurityGateway.logging       back to default value.     --logging=[LOGGING,...]      Configuration for Cloud Logging.      Shorthand Example:        --logging=      JSON Example:        --logging={}      File Example:        --logging=path_to_file.(yaml|json)    The configuration for the proxy.
+    /// An optional request ID to identify requests. Specify a unique request     ID so that if you must retry your request, the server will know to     ignore the request if it has already been completed. The server will     guarantee that for at least 60 minutes after the first request.     For example, consider a situation where you make an initial request and     the request timed out. If you make the request again with the same     request ID, the server can check if original operation with the same     request ID was received, and if so, will ignore the second request.     This prevents clients from accidentally creating duplicate commitments.     The request ID must be a valid UUID with the exception that zero UUID     is not supported (00000000-0000-0000-0000-000000000000).    The configuration for the proxy.
     /// </summary>
     [CliOption("--request-id", Format = OptionFormat.EqualsSeparated)]
     public string? RequestId { get; set; }

src/ModularPipelines.Google/Options/GcloudBiglakeIcebergCatalogsUpdateOptions.Generated.cs

@@ -26,7 +26,7 @@ public record GcloudBiglakeIcebergCatalogsUpdateOptions : GcloudOptions
     public string? CredentialMode { get; set; }
 
     /// <summary>
-    /// Description of the resource being created.
+    /// Description of the resource.
     /// </summary>
     [CliOption("--description", Format = OptionFormat.EqualsSeparated)]
     public string? Description { get; set; }

src/ModularPipelines.Google/Options/GcloudBigtableInstancesTablesUpdateOptions.Generated.cs

@@ -34,7 +34,7 @@ public record GcloudBigtableInstancesTablesUpdateOptions : GcloudOptions
     public bool? DeletionProtection { get; set; }
 
     /// <summary>
-    /// By default, Base64 encoding is applied to all binary fields in the     YAML/JSON file (for example, encoding.delimitedBytes.delimiter).     Use this to indicate that all binary fields are already encoded in the     YAML/JSON file and should not be encoded again.     This field is only used when row-key-schema-definition-file is set. It     is ignored if clear-row-key-schema is set.    At most one of these can be specified:     --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD      The retention period of automated backup in the format of 30d for 30      days. Min retention period is 3d and max is 90d. Setting this flag      will enable automated backup for the table.     --disable-automated-backup      Once set, disables automated backup policy for the table.     --enable-automated-backup      Once set, enables the default automated backup policy      (retention_period=7d, frequency=1d) for the table. Note: If a table      has automated backup enabled, this flag resets it to the default      policy.    At most one of these can be specified:     --change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD      The length of time to retain change stream data for the table, in the      range of [1 day, 7 days]. Acceptable units are days (d), hours (h),      minutes (m), and seconds (s). If not already specified, enables a      change stream for the table. Examples: 5d or 48h.     --clear-change-stream-retention-period      This disables the change stream and eventually removes the change      stream data.    Whether to update or clear the row key schema in the updated table. Only   one of these flags can be set.    At most one of these can be specified:     --clear-row-key-schema      Whether to clear the row key schema in the updated table.     --row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE      The row key schema for the table. The schema is defined in a YAML or      JSON file, equivalent to the StructType protobuf message.      Example YAML:        encoding:         delimitedBytes:          delimiter: '#'        fields:        - fieldName: field1         type:          bytesType:           encoding:            raw: {}        - fieldName: field2         type:          bytesType:           encoding:            raw: {}
+    /// By default, Base64 encoding is applied to all binary fields in the     YAML/JSON file (for example, encoding.delimitedBytes.delimiter).     Use this to indicate that all binary fields are already encoded in the     YAML/JSON file and should not be encoded again.     This field is only used when row-key-schema-definition-file is set. It     is ignored if clear-row-key-schema is set.    At most one of these can be specified:     Group for automated backup policy parameters.     --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD      The retention period of automated backup in the format of 30d for 30      days. Min retention period is 3d and max is 90d. Setting this flag      will enable automated backup for the table.     At most one of these can be specified:      --automated-backup-locations=[LOCATION,...]       List of Cloud Bigtable zones where automated backups are allowed to       be created. If empty, automated backups will be created in all       zones of the instance. Locations are in the format       projects/{project}/locations/{zone}. Setting this flag will enable       automated backup for the table.      --clear-automated-backup-locations       Empty the automated backup locations list if populated.     At most one of these can be specified:      --disable-automated-backup       Once set, disables automated backup policy for the table.      --enable-automated-backup       Once set, enables the default automated backup policy       (retention_period=7d, frequency=1d) for the table. Note: If a table       has automated backup enabled, this flag resets it to the default       policy.    At most one of these can be specified:     --change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD      The length of time to retain change stream data for the table, in the      range of [1 day, 7 days]. Acceptable units are days (d), hours (h),      minutes (m), and seconds (s). If not already specified, enables a      change stream for the table. Examples: 5d or 48h.     --clear-change-stream-retention-period      This disables the change stream and eventually removes the change      stream data.    Whether to update or clear the row key schema in the updated table. Only   one of these flags can be set.    At most one of these can be specified:     --clear-row-key-schema      Whether to clear the row key schema in the updated table.     --row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE      The row key schema for the table. The schema is defined in a YAML or      JSON file, equivalent to the StructType protobuf message.      Example YAML:        encoding:         delimitedBytes:          delimiter: '#'        fields:        - fieldName: field1         type:          bytesType:           encoding:            raw: {}        - fieldName: field2         type:          bytesType:           encoding:            raw: {}
     /// </summary>
     [CliFlag("--row-key-schema-pre-encoded-bytes")]
     public bool? RowKeySchemaPreEncodedBytes { get; set; }

src/ModularPipelines.Google/Options/GcloudBigtableTablesUpdateOptions.Generated.cs

@@ -34,7 +34,7 @@ public record GcloudBigtableTablesUpdateOptions : GcloudOptions
     public bool? DeletionProtection { get; set; }
 
     /// <summary>
-    /// By default, Base64 encoding is applied to all binary fields in the     YAML/JSON file (for example, encoding.delimitedBytes.delimiter).     Use this to indicate that all binary fields are already encoded in the     YAML/JSON file and should not be encoded again.     This field is only used when row-key-schema-definition-file is set. It     is ignored if clear-row-key-schema is set.    At most one of these can be specified:     --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD      The retention period of automated backup in the format of 30d for 30      days. Min retention period is 3d and max is 90d. Setting this flag      will enable automated backup for the table.     --disable-automated-backup      Once set, disables automated backup policy for the table.     --enable-automated-backup      Once set, enables the default automated backup policy      (retention_period=7d, frequency=1d) for the table. Note: If a table      has automated backup enabled, this flag resets it to the default      policy.    At most one of these can be specified:     --change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD      The length of time to retain change stream data for the table, in the      range of [1 day, 7 days]. Acceptable units are days (d), hours (h),      minutes (m), and seconds (s). If not already specified, enables a      change stream for the table. Examples: 5d or 48h.     --clear-change-stream-retention-period      This disables the change stream and eventually removes the change      stream data.    Whether to update or clear the row key schema in the updated table. Only   one of these flags can be set.    At most one of these can be specified:     --clear-row-key-schema      Whether to clear the row key schema in the updated table.     --row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE      The row key schema for the table. The schema is defined in a YAML or      JSON file, equivalent to the StructType protobuf message.      Example YAML:        encoding:         delimitedBytes:          delimiter: '#'        fields:        - fieldName: field1         type:          bytesType:           encoding:            raw: {}        - fieldName: field2         type:          bytesType:           encoding:            raw: {}
+    /// By default, Base64 encoding is applied to all binary fields in the     YAML/JSON file (for example, encoding.delimitedBytes.delimiter).     Use this to indicate that all binary fields are already encoded in the     YAML/JSON file and should not be encoded again.     This field is only used when row-key-schema-definition-file is set. It     is ignored if clear-row-key-schema is set.    At most one of these can be specified:     Group for automated backup policy parameters.     --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD      The retention period of automated backup in the format of 30d for 30      days. Min retention period is 3d and max is 90d. Setting this flag      will enable automated backup for the table.     At most one of these can be specified:      --automated-backup-locations=[LOCATION,...]       List of Cloud Bigtable zones where automated backups are allowed to       be created. If empty, automated backups will be created in all       zones of the instance. Locations are in the format       projects/{project}/locations/{zone}. Setting this flag will enable       automated backup for the table.      --clear-automated-backup-locations       Empty the automated backup locations list if populated.     At most one of these can be specified:      --disable-automated-backup       Once set, disables automated backup policy for the table.      --enable-automated-backup       Once set, enables the default automated backup policy       (retention_period=7d, frequency=1d) for the table. Note: If a table       has automated backup enabled, this flag resets it to the default       policy.    At most one of these can be specified:     --change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD      The length of time to retain change stream data for the table, in the      range of [1 day, 7 days]. Acceptable units are days (d), hours (h),      minutes (m), and seconds (s). If not already specified, enables a      change stream for the table. Examples: 5d or 48h.     --clear-change-stream-retention-period      This disables the change stream and eventually removes the change      stream data.    Whether to update or clear the row key schema in the updated table. Only   one of these flags can be set.    At most one of these can be specified:     --clear-row-key-schema      Whether to clear the row key schema in the updated table.     --row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE      The row key schema for the table. The schema is defined in a YAML or      JSON file, equivalent to the StructType protobuf message.      Example YAML:        encoding:         delimitedBytes:          delimiter: '#'        fields:        - fieldName: field1         type:          bytesType:           encoding:            raw: {}        - fieldName: field2         type:          bytesType:           encoding:            raw: {}
     /// </summary>
     [CliFlag("--row-key-schema-pre-encoded-bytes")]
     public bool? RowKeySchemaPreEncodedBytes { get; set; }

src/ModularPipelines.Google/Options/GcloudComputeCompositeHealthChecksCreateOptions.Generated.cs

@@ -0,0 +1,24 @@
+// <auto-generated>
+// This file was generated by ModularPipelines.OptionsGenerator.
+// Source: https://cloud.google.com/sdk/gcloud/reference/compute/composite-health-checks/create
+// Do not edit this file manually.
+// </auto-generated>
+
+#nullable enable
+
+using System.CodeDom.Compiler;
+using System.Diagnostics.CodeAnalysis;
+using ModularPipelines.Attributes;
+using ModularPipelines.Google.Options;
+
+namespace ModularPipelines.Google.Options;
+
+/// <summary>
+/// create a composite health     check
+/// </summary>
+[GeneratedCode("ModularPipelines.OptionsGenerator", "")]
+[ExcludeFromCodeCoverage]
+[CliSubCommand("compute", "composite-health-checks", "create")]
+public record GcloudComputeCompositeHealthChecksCreateOptions : GcloudOptions
+{
+}

src/ModularPipelines.Google/Options/GcloudComputeCompositeHealthChecksDeleteOptions.Generated.cs

@@ -0,0 +1,30 @@
+// <auto-generated>
+// This file was generated by ModularPipelines.OptionsGenerator.
+// Source: https://cloud.google.com/sdk/gcloud/reference/compute/composite-health-checks/delete
+// Do not edit this file manually.
+// </auto-generated>
+
+#nullable enable
+
+using System.CodeDom.Compiler;
+using System.Diagnostics.CodeAnalysis;
+using ModularPipelines.Attributes;
+using ModularPipelines.Google.Options;
+
+namespace ModularPipelines.Google.Options;
+
+/// <summary>
+/// delete a composite health     check
+/// </summary>
+[GeneratedCode("ModularPipelines.OptionsGenerator", "")]
+[ExcludeFromCodeCoverage]
+[CliSubCommand("compute", "composite-health-checks", "delete")]
+public record GcloudComputeCompositeHealthChecksDeleteOptions : GcloudOptions
+{
+    /// <summary>
+    /// Return immediately, without waiting for the operation in progress to     complete.
+    /// </summary>
+    [CliFlag("--async")]
+    public bool? Async { get; set; }
+
+}