Bump, oxide.json to omicron:9e58f1bb (#764)

Co-authored-by: oxide-reflector-bot[bot] <130185838+oxide-reflector-bot[bot]@users.noreply.github.com>

Author: oxide-reflector-bot[bot]

cli/docs/cli.json

@@ -4176,7 +4176,7 @@
             {
               "name": "update",
               "about": "Replace firewall rules",
-              "long_about": "The maximum number of rules per VPC is 1024.\nTargets are used to specify the set of instances to which a firewall rule applies. You can target instances directly by name, or specify a VPC, VPC subnet, IP, or IP subnet, which will apply the rule to traffic going to all matching instances. Targets are additive: the rule applies to instances matching ANY target. The maximum number of targets is 256.\nFilters reduce the scope of a firewall rule. Without filters, the rule applies to all packets to the targets (or from the targets, if it's an outbound rule). With multiple filters, the rule applies only to packets matching ALL filters. The maximum number of each type of filter is 256.",
+              "long_about": "The maximum number of rules per VPC is 1024.\n\nTargets are used to specify the set of instances to which a firewall rule applies. You can target instances directly by name, or specify a VPC, VPC subnet, IP, or IP subnet, which will apply the rule to traffic going to all matching instances. Targets are additive: the rule applies to instances matching ANY target. The maximum number of targets is 256.\n\nFilters reduce the scope of a firewall rule. Without filters, the rule applies to all packets to the targets (or from the targets, if it's an outbound rule). With multiple filters, the rule applies only to packets matching ALL filters. The maximum number of each type of filter is 256.",
               "args": [
                 {
                   "long": "json-body",

cli/src/generated_cli.rs

@@ -5075,15 +5075,15 @@ impl<T: CliConfig> Cli<T> {
             )
             .about("Replace firewall rules")
             .long_about(
-                "The maximum number of rules per VPC is 1024.\nTargets are used to specify the \
+                "The maximum number of rules per VPC is 1024.\n\nTargets are used to specify the \
                  set of instances to which a firewall rule applies. You can target instances \
                  directly by name, or specify a VPC, VPC subnet, IP, or IP subnet, which will \
                  apply the rule to traffic going to all matching instances. Targets are additive: \
                  the rule applies to instances matching ANY target. The maximum number of targets \
-                 is 256.\nFilters reduce the scope of a firewall rule. Without filters, the rule \
-                 applies to all packets to the targets (or from the targets, if it's an outbound \
-                 rule). With multiple filters, the rule applies only to packets matching ALL \
-                 filters. The maximum number of each type of filter is 256.",
+                 is 256.\n\nFilters reduce the scope of a firewall rule. Without filters, the \
+                 rule applies to all packets to the targets (or from the targets, if it's an \
+                 outbound rule). With multiple filters, the rule applies only to packets matching \
+                 ALL filters. The maximum number of each type of filter is 256.",
             )
     }
 

oxide.json

@@ -8297,7 +8297,7 @@
           "vpcs"
         ],
         "summary": "Replace firewall rules",
-        "description": "The maximum number of rules per VPC is 1024.\nTargets are used to specify the set of instances to which a firewall rule applies. You can target instances directly by name, or specify a VPC, VPC subnet, IP, or IP subnet, which will apply the rule to traffic going to all matching instances. Targets are additive: the rule applies to instances matching ANY target. The maximum number of targets is 256.\nFilters reduce the scope of a firewall rule. Without filters, the rule applies to all packets to the targets (or from the targets, if it's an outbound rule). With multiple filters, the rule applies only to packets matching ALL filters. The maximum number of each type of filter is 256.",
+        "description": "The maximum number of rules per VPC is 1024.\n\nTargets are used to specify the set of instances to which a firewall rule applies. You can target instances directly by name, or specify a VPC, VPC subnet, IP, or IP subnet, which will apply the rule to traffic going to all matching instances. Targets are additive: the rule applies to instances matching ANY target. The maximum number of targets is 256.\n\nFilters reduce the scope of a firewall rule. Without filters, the rule applies to all packets to the targets (or from the targets, if it's an outbound rule). With multiple filters, the rule applies only to packets matching ALL filters. The maximum number of each type of filter is 256.",
         "operationId": "vpc_firewall_rules_update",
         "parameters": [
           {

sdk/src/generated_sdk.rs

@@ -49397,11 +49397,13 @@ pub trait ClientVpcsExt {
     /// Replace firewall rules
     ///
     /// The maximum number of rules per VPC is 1024.
+    ///
     /// Targets are used to specify the set of instances to which a firewall
     /// rule applies. You can target instances directly by name, or specify a
     /// VPC, VPC subnet, IP, or IP subnet, which will apply the rule to traffic
     /// going to all matching instances. Targets are additive: the rule applies
     /// to instances matching ANY target. The maximum number of targets is 256.
+    ///
     /// Filters reduce the scope of a firewall rule. Without filters, the rule
     /// applies to all packets to the targets (or from the targets, if it's an
     /// outbound rule). With multiple filters, the rule applies only to packets