fix hidden flag property

Author: stephanos

internal/commandsgen/code.go

@@ -492,5 +492,8 @@ func (o *Option) writeFlagBuilding(selfVar, flagVar string, w *codeWriter) error
 	if o.Deprecated != "" {
 		w.writeLinef("_ = %v.MarkDeprecated(%q, %q)", flagVar, o.Name, o.Deprecated)
 	}
+	if o.Hidden {
+		w.writeLinef("_ = %v.MarkHidden(%q)", flagVar, o.Name)
+	}
 	return nil
 }

internal/commandsgen/parse.go

@@ -28,6 +28,7 @@ type (
 		Aliases            []string `yaml:"aliases,omitempty"`
 		EnumValues         []string `yaml:"enum-values,omitempty"`
 		Experimental       bool     `yaml:"experimental,omitempty"`
+		Hidden             bool     `yaml:"hidden,omitempty"`
 		HiddenLegacyValues []string `yaml:"hidden-legacy-values,omitempty"`
 	}
 

internal/temporalcli/commands.gen.go

@@ -2275,9 +2275,11 @@ func NewTemporalTaskQueueConfigSetCommand(cctx *CommandContext, parent *Temporal
 	s.Command.Flags().StringVar(&s.QueueRpsLimit, "queue-rps-limit", "", "Queue rate limit in requests per second. Accepts a float; or 'default' to unset.")
 	overrideFlagDisplayType(s.Command.Flags().Lookup("queue-rps-limit"), "float|default")
 	s.Command.Flags().StringVar(&s.QueueRpsLimitReason, "queue-rps-limit-reason", "", "Reason for queue rate limit update.")
+	_ = s.Command.Flags().MarkHidden("queue-rps-limit-reason")
 	s.Command.Flags().StringVar(&s.FairnessKeyRpsLimitDefault, "fairness-key-rps-limit-default", "", "Fairness key rate limit default in requests per second. Accepts a float; or 'default' to unset.")
 	overrideFlagDisplayType(s.Command.Flags().Lookup("fairness-key-rps-limit-default"), "float|default")
 	s.Command.Flags().StringVar(&s.FairnessKeyRpsLimitReason, "fairness-key-rps-limit-reason", "", "Reason for fairness key rate limit update.")
+	_ = s.Command.Flags().MarkHidden("fairness-key-rps-limit-reason")
 	s.Command.Run = func(c *cobra.Command, args []string) {
 		if err := s.run(cctx, args); err != nil {
 			cctx.Options.Fail(err)

internal/temporalcli/commands.yaml

@@ -360,7 +360,7 @@ commands:
 
       Either `activity-id`, `activity-type`, or `--match-all` must be specified.
 
-      Activity options can be updated in bulk with a visibility query list filter. 
+      Activity options can be updated in bulk with a visibility query list filter.
       For example, if you want to reset for activities of type Foo, do:
 
       ```
@@ -592,7 +592,7 @@ commands:
 
       Either `activity-id`, `activity-type`, or `--match-all` must be specified.
 
-      Activities can be reset in bulk with a visibility query list filter. 
+      Activities can be reset in bulk with a visibility query list filter.
       For example, if you want to reset activities of type Foo:
 
       ```
@@ -1274,17 +1274,17 @@ commands:
       ```
       temporal worker deployment manager-identity [command] [options]
       ```
-      
-      When present, `ManagerIdentity` is the identity of the user that has the 
+
+      When present, `ManagerIdentity` is the identity of the user that has the
       exclusive right to make changes to this Worker Deployment. Empty by default.
       When set, users whose identity does not match the `ManagerIdentity` will not
       be able to change the Worker Deployment.
-  
+
       This is especially useful in environments where multiple users (such as CLI
       users and automated controllers) may interact with the same Worker Deployment.
       `ManagerIdentity` allows different users to communicate with one another about
       who is expected to make changes to the Worker Deployment.
-      
+
       The current Manager Identity is returned with `describe`:
       ```
        temporal worker deployment describe \
@@ -1310,12 +1310,12 @@ commands:
       ```
 
       Set the `ManagerIdentity` of a Worker Deployment given its Deployment Name.
-      
-      When present, `ManagerIdentity` is the identity of the user that has the 
+
+      When present, `ManagerIdentity` is the identity of the user that has the
       exclusive right to make changes to this Worker Deployment. Empty by default.
       When set, users whose identity does not match the `ManagerIdentity` will not
       be able to change the Worker Deployment.
-  
+
       This is especially useful in environments where multiple users (such as CLI
       users and automated controllers) may interact with the same Worker Deployment.
       `ManagerIdentity` allows different users to communicate with one another about
@@ -1324,7 +1324,7 @@ commands:
       ```
       temporal worker deployment manager-identity set [options]
       ```
-      
+
       For example:
 
       ```
@@ -1334,17 +1334,17 @@ commands:
          --identity YourUserIdentity # optional, populated by CLI if not provided
       ```
 
-      Sets the Manager Identity of the Deployment to the identity of the user making 
-      this request. If you don't specifically pass an identity field, the CLI will 
+      Sets the Manager Identity of the Deployment to the identity of the user making
+      this request. If you don't specifically pass an identity field, the CLI will
       generate your identity for you.
-      
+
       For example:
       ```
       temporal worker deployment manager-identity set \
          --deployment-name DeploymentName \
          --manager-identity NewManagerIdentity
       ```
-      
+
       Sets the Manager Identity of the Deployment to any string.
 
     options:
@@ -1373,12 +1373,12 @@ commands:
       ```
 
       Unset the `ManagerIdentity` of a Worker Deployment given its Deployment Name.
-      
-      When present, `ManagerIdentity` is the identity of the user that has the 
+
+      When present, `ManagerIdentity` is the identity of the user that has the
       exclusive right to make changes to this Worker Deployment. Empty by default.
       When set, users whose identity does not match the `ManagerIdentity` will not
       be able to change the Worker Deployment.
-      
+
       This is especially useful in environments where multiple users (such as CLI
       users and automated controllers) may interact with the same Worker Deployment.
       `ManagerIdentity` allows different users to communicate with one another about
@@ -1387,7 +1387,7 @@ commands:
       ```
       temporal worker deployment manager-identity unset [options]
       ```
-      
+
       For example:
 
       ```
@@ -1410,7 +1410,7 @@ commands:
     summary: List worker status information in a specific namespace (EXPERIMENTAL)
     description: |
       Get a list of workers to the specified namespace.
-      
+
       ```
       temporal worker list --namespace YourNamespace --query 'TaskQueue="YourTaskQueue"'
       ```
@@ -1427,7 +1427,7 @@ commands:
     summary: Returns information about a specific worker (EXPERIMENTAL)
     description: |
       Look up information of a specific worker.
-      
+
       ```
       temporal worker describe --namespace YourNamespace --worker-instance-key YourKey
       ```
@@ -3475,7 +3475,6 @@ commands:
       - name: queue-rps-limit-reason
         type: string
         description: Reason for queue rate limit update.
-        hidden: true
       - name: fairness-key-rps-limit-default
         type: string
         display-type: float|default
@@ -3485,7 +3484,6 @@ commands:
       - name: fairness-key-rps-limit-reason
         type: string
         description: Reason for fairness key rate limit update.
-        hidden: true
 
   - name: temporal workflow
     summary: Start, list, and operate on Workflows
@@ -4979,7 +4977,7 @@ option-sets:
           Temporal workflow headers in 'KEY=VALUE' format.
           Keys must be identifiers, and values must be JSON values.
           May be passed multiple times to set multiple Temporal headers.
-          Note: These are workflow headers, not gRPC headers.   
+          Note: These are workflow headers, not gRPC headers.
 
   - name: workflow-update-options
     options: