OAS Update

Author: stackit-pipeline

services/load-balancer/v2/load-balancer.json

@@ -145,6 +145,15 @@
             },
             "type": "array"
           },
+          "targetSecurityGroup": {
+            "allOf": [
+              {
+                "$ref": "#/components/schemas/SecurityGroup"
+              }
+            ],
+            "description": "Security Group permitting network traffic from the LoadBalancer to the targets.",
+            "readOnly": true
+          },
           "version": {
             "description": "Load balancer resource version.\nMust be empty or unset for creating load balancers, non-empty for updating load balancers. Semantics:\nWhile retrieving load balancers, this is the current version of this load balancer resource that changes during updates of the load balancers. On updates this field specified the load balancer version you calculated your update for instead of the future version to enable concurrency safe updates. Update calls will then report the new version in their result as you would see with a load balancer retrieval call later. There exist no total order of the version, so you can only compare it for equality, but not for less/greater than another version. Since the creation of load balancer is always intended to create the first version of it, there should be no existing version. That's why this field must by empty of not present in that case.",
             "example": "lb-238165323",
@@ -397,6 +406,15 @@
             },
             "type": "array"
           },
+          "targetSecurityGroup": {
+            "allOf": [
+              {
+                "$ref": "#/components/schemas/SecurityGroup"
+              }
+            ],
+            "description": "Security Group permitting network traffic from the LoadBalancer to the targets.",
+            "readOnly": true
+          },
           "version": {
             "description": "Load balancer resource version.\nMust be empty or unset for creating load balancers, non-empty for updating load balancers. Semantics:\nWhile retrieving load balancers, this is the current version of this load balancer resource that changes during updates of the load balancers. On updates this field specified the load balancer version you calculated your update for instead of the future version to enable concurrency safe updates. Update calls will then report the new version in their result as you would see with a load balancer retrieval call later. There exist no total order of the version, so you can only compare it for equality, but not for less/greater than another version. Since the creation of load balancer is always intended to create the first version of it, there should be no existing version. That's why this field must by empty of not present in that case.",
             "example": "lb-238165323",
@@ -590,6 +608,19 @@
         },
         "type": "object"
       },
+      "SecurityGroup": {
+        "properties": {
+          "id": {
+            "description": "ID of the security Group",
+            "type": "string"
+          },
+          "name": {
+            "description": "Name of the security Group",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
       "ServerNameIndicator": {
         "properties": {
           "name": {
@@ -782,6 +813,15 @@
             },
             "type": "array"
           },
+          "targetSecurityGroup": {
+            "allOf": [
+              {
+                "$ref": "#/components/schemas/SecurityGroup"
+              }
+            ],
+            "description": "Security Group permitting network traffic from the LoadBalancer to the targets.",
+            "readOnly": true
+          },
           "version": {
             "description": "Load balancer resource version.\nMust be empty or unset for creating load balancers, non-empty for updating load balancers. Semantics:\nWhile retrieving load balancers, this is the current version of this load balancer resource that changes during updates of the load balancers. On updates this field specified the load balancer version you calculated your update for instead of the future version to enable concurrency safe updates. Update calls will then report the new version in their result as you would see with a load balancer retrieval call later. There exist no total order of the version, so you can only compare it for equality, but not for less/greater than another version. Since the creation of load balancer is always intended to create the first version of it, there should be no existing version. That's why this field must by empty of not present in that case.",
             "example": "lb-238165323",