fix MegaLinter

Author: FabrizioMoggio

code/API_definitions/Traffic_Influence.yaml

@@ -151,8 +151,8 @@ info:
     The traffic can be from a specific application port in the Device.\
     \
     **destinationTrafficFilters:**
-    The Application can expose different service on different interfaces, 
-    identified by port and protocol, with this parameter it is possible to 
+    The Application can expose different service on different interfaces,
+    identified by port and protocol, with this parameter it is possible to
     route the traffic just toward some of those services maybe for different
     sets of users.\
     \
@@ -659,7 +659,7 @@ components:
            specified application server address and ports.
           type: object
           properties:
-            sourcePort:           
+            sourcePort:
               allOf:
                 - $ref: "#/components/schemas/PortsSpec"
         destinationTrafficFilters:
@@ -669,7 +669,7 @@ components:
            (e.g. TCP or UDP) can be specified.
           type: object
           properties:
-            destinationPort:           
+            destinationPort:
               allOf:
                 - $ref: "#/components/schemas/PortsSpec"
             destinationProtocol:
@@ -731,84 +731,84 @@ components:
       type: string
       additionalProperties: false
     Device:
-     description: |
-      End-user equipment able to connect to a mobile network. Examples of
-        devices include smartphones or IoT sensors/actuators.
-        The developer can choose to provide the below specified device
-        identifiers:
-        * `ipv4Address`
-        * `ipv6Address`
-        * `phoneNumber`
-        * `networkAccessIdentifier`
-        NOTE: the MNO might support only a subset of these options. The API
-        invoker can provide multiple identifiers to be compatible across
-        different MNOs. In this case the identifiers MUST belong to the same
-        device.
-     type: object
-     properties:
-      phoneNumber:
-       $ref: "#/components/schemas/PhoneNumber"
-      networkAccessIdentifier:
-       $ref: "#/components/schemas/NetworkAccessIdentifier"
-      ipv4Address:
-       $ref: "#/components/schemas/DeviceIpv4Addr"
-      ipv6Address:
-       $ref: "#/components/schemas/DeviceIpv6Address"
-     minProperties: 1
+      description: |
+         End-user equipment able to connect to a mobile network. Examples of
+           devices include smartphones or IoT sensors/actuators.
+           The developer can choose to provide the below specified device
+           identifiers:
+           * `ipv4Address`
+           * `ipv6Address`
+           * `phoneNumber`
+           * `networkAccessIdentifier`
+           NOTE: the MNO might support only a subset of these options. The API
+           invoker can provide multiple identifiers to be compatible across
+           different MNOs. In this case the identifiers MUST belong to the same
+           device.
+      type: object
+      properties:
+        phoneNumber:
+          $ref: "#/components/schemas/PhoneNumber"
+        networkAccessIdentifier:
+          $ref: "#/components/schemas/NetworkAccessIdentifier"
+        ipv4Address:
+          $ref: "#/components/schemas/DeviceIpv4Addr"
+        ipv6Address:
+          $ref: "#/components/schemas/DeviceIpv6Address"
+      minProperties: 1
     PhoneNumber:
-     description: A public identifier addressing a telephone subscription. In
-       mobile networks it corresponds to the MSISDN (Mobile Station
-       International Subscriber Directory Number). In order to be globally
-       unique it has to be formatted in international format, according to
-       E.164 standard, prefixed with '+'.
-     type: string
-     pattern: '^\+[1-9][0-9]{4,14}$'
-     example: "+123456789"
+      description: A public identifier addressing a telephone subscription. In
+        mobile networks it corresponds to the MSISDN (Mobile Station
+        International Subscriber Directory Number). In order to be globally
+        unique it has to be formatted in international format, according to
+        E.164 standard, prefixed with '+'.
+      type: string
+      pattern: '^\+[1-9][0-9]{4,14}$'
+      example: "+123456789"
     NetworkAccessIdentifier:
-     description: A public identifier addressing a subscription in a mobile
-       network. In 3GPP terminology, it corresponds to the GPSI formatted with
-       the External Identifier ({Local Identifier}@{Domain Identifier}).
-       Unlike the telephone number, the network access identifier is not
-       subjected to portability ruling in force, and is individually managed
-       by each operator.
-     type: string
-     example: "[email protected]"
+      description: A public identifier addressing a subscription in a mobile
+        network. In 3GPP terminology, it corresponds to the GPSI formatted with
+        the External Identifier ({Local Identifier}@{Domain Identifier}).
+        Unlike the telephone number, the network access identifier is not
+        subjected to portability ruling in force, and is individually managed
+        by each operator.
+      type: string
+      example: "[email protected]"
     DeviceIpv4Addr:
-     type: object
-     description: |
-      The device should be identified by either the public (observed) IP address
-        and port as seen by the application server, or the private (local) and
-        any public (observed) IP addresses in use by the device (this
-        information can be obtained by various means, for example from some DNS
-        servers).
-      If the allocated and observed IP addresses are the same (i.e. NAT is not
-        in use) then  the same address should be specified for both publicAddress
-       and privateAddress.
-      If NAT64 is in use, the device should be identified by its publicAddress
-        and publicPort, or separately by its allocated IPv6 address (field
-        ipv6Address of the Device object)
-      In all cases, publicAddress must be specified, along with at least one
-        of either privateAddress or publicPort, dependent upon which is known.
-        In general, mobile devices cannot be identified by their public IPv4
-        address alone.
-     properties:
-      publicAddress:
-       $ref: "#/components/schemas/SingleIpv4Addr"
-      privateAddress:
-       $ref: "#/components/schemas/SingleIpv4Addr"
-      publicPort:
-       $ref: "#/components/schemas/Port"
-     anyOf:
-      - required: [publicAddress, privateAddress]
-      - required: [publicAddress, publicPort]
-     example:
-      publicAddress: "84.125.93.10"
-      publicPort: 59765
+      type: object
+      description: |
+        The device should be identified by either the public (observed) IP address
+          and port as seen by the application server, or the private (local) and
+          any public (observed) IP addresses in use by the device (this
+          information can be obtained by various means, for example from some DNS
+          servers).
+        If the allocated and observed IP addresses are the same (i.e. NAT is not
+          in use) then  the same address should be specified for both publicAddress
+          and privateAddress.
+        If NAT64 is in use, the device should be identified by its publicAddress
+          and publicPort, or separately by its allocated IPv6 address (field
+          ipv6Address of the Device object)
+        In all cases, publicAddress must be specified, along with at least one
+          of either privateAddress or publicPort, dependent upon which is known.
+          In general, mobile devices cannot be identified by their public IPv4
+          address alone.
+      properties:
+        publicAddress:
+          $ref: "#/components/schemas/SingleIpv4Addr"
+        privateAddress:
+          $ref: "#/components/schemas/SingleIpv4Addr"
+        publicPort:
+          $ref: "#/components/schemas/Port"
+      anyOf:
+        - required: [publicAddress, privateAddress]
+        - required: [publicAddress, publicPort]
+      example:
+        publicAddress: "84.125.93.10"
+        publicPort: 59765
     SingleIpv4Addr:
-     description: A single IPv4 address with no subnet mask
-     type: string
-     format: ipv4
-     example: "84.125.93.10"
+      description: A single IPv4 address with no subnet mask
+      type: string
+      format: ipv4
+      example: "84.125.93.10"
     PortsSpec:
       description: Specification of several TCP or UDP ports
       type: object
@@ -829,10 +829,10 @@ components:
               to:
                 $ref: "#/components/schemas/Port"
     Port:
-     description: TCP or UDP port number
-     type: integer
-     minimum: 0
-     maximum: 65535
+      description: TCP or UDP port number
+      type: integer
+      minimum: 0
+      maximum: 65535
     Protocol:
       description: The protocol for the influeced flow. It can be specified and
        it is identified by a string according to the column “Keyword” as defined
@@ -841,13 +841,13 @@ components:
       type: string 
       example: "TCP"
     DeviceIpv6Address:
-     description: |
-      The device should be identified by the observed IPv6 address, or by any
-        single IPv6 address from within the subnet allocated to the device (e.g.
-        adding ::0 to the /64 prefix).
-     type: string
-     format: ipv6
-     example: 2001:db8:85a3:8d3:1319:8a2e:370:7344
+      description: |
+       The device should be identified by the observed IPv6 address, or by any
+         single IPv6 address from within the subnet allocated to the device (e.g.
+         adding ::0 to the /64 prefix).
+      type: string
+      format: ipv6
+      example: 2001:db8:85a3:8d3:1319:8a2e:370:7344
     AppInstanceId:
       type: string
       format: uuid