Update EdgeCloud_LcM.yaml to harmonize EdgeCloudZone

Added EdgeCloudeZone schema to harmonize with SED.
Updated version to 0.9.2, as relevant changes are made.
Adaptation of the format to the MegalinterWorkflow criteria.

Author: javierlozallu

code/API_definitions/EdgeCloud_LcM.yaml

@@ -515,10 +515,13 @@ components:
           $ref: '#/components/schemas/EdgeCloudZone'
 
     AppZones:
+      description: Collection of Edge Cloud Zones where the AP wants to
+        instantiate the application.
       type: array
       items:
         $ref: '#/components/schemas/EdgeCloudZone'
       minItems: 1
+      additionalProperties: false
 
     AppManifest:
       properties:
@@ -606,8 +609,9 @@ components:
                 type: string
                 description: Component name must be unique with an application
               networkInterfaces:
-                description: Each application component exposes some ports either
-                  for external users or for inter component communication.
+                description: Each application component exposes some ports 
+                  either for external users or for inter component
+                  communication.
                   Application provider is required to specify which ports are 
                   to be exposed and the type of traffic that will flow through
                   these ports.The underlying platform may assign a dynamic port
@@ -660,7 +664,6 @@ components:
                         - VISIBILITY_EXTERNAL
                         - VISIBILITY_INTERNAL
                 minItems: 1                
-
       required:
         - name
         - version
@@ -679,13 +682,14 @@ components:
         the Edge Cloud. Defined by the Edge Provider.
 
     EdgeCloudZones:
-      description: A collection of Edge Cloud Zones where the AP can
-        instantiate an Application Instance.
       type: array
       items:
         $ref: '#/components/schemas/EdgeCloudZone'
       minItems: 1
- 
+      description: A collection of Edge Cloud Zones where the AP can
+        instantiate an Application Instance.
+      additionalProperties: false
+
     EdgeCloudZoneId:
       type: string
       format: uuid
@@ -758,14 +762,19 @@ components:
 
     Ipv4Addr:
       type: string
-      pattern: ^(([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\.){3}([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])$
+      pattern: |
+       ^(([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\.){3}([0-9]
+       |[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])$
       example: 198.51.100.1
 
     Ipv6Addr:
       type: string
       allOf:
-        - pattern: ^((:|(0?|([1-9a-f][0-9a-f]{0,3}))):)((0?|([1-9a-f][0-9a-f]{0,3})):){0,6}(:|(0?|([1-9a-f][0-9a-f]{0,3})))$
-        - pattern: ^((([^:]+:){7}([^:]+))|((([^:]+:)*[^:]+)?::(([^:]+:)*[^:]+)?))$
+        - pattern: |
+            ^((:|(0?|([1-9a-f][0-9a-f]{0,3}))):)((0?
+            |([1-9a-f][0-9a-f]{0,3})):){0,6}(:|(0?|([1-9a-f][0-9a-f]{0,3})))$
+        - pattern: |
+            ^((([^:]+:){7}([^:]+))|((([^:]+:)*[^:]+)?::(([^:]+:)*[^:]+)?))$
       example: 2001:db8:85a3::8a2e:370:7334
 
     OperatingSystem: