Commit 980c9e2f authored by M. Rehan Abbasi's avatar M. Rehan Abbasi
Browse files

reformat MEC011 OAS yaml files

parent 4ff90c47
Loading
Loading
Loading
Loading
+164 −164

File changed.

Preview size limit exceeded, changes collapsed.

+47 −47
Original line number Diff line number Diff line
openapi: 3.0.2
openapi: 3.0.0
servers:
  - url: 'https://localhost/sandboxname/mec_service_mgmt/v1'
info:
  title: MEC Service Management API
  version: 2.2.1
  description: 'The ETSI MEC ISG MEC011 MEC Service Management API described using OpenAPI.
  description:
    'The ETSI MEC ISG MEC011 MEC Service Management API described using OpenAPI.
    <p>**Note**<br>MEC Sandbox supports all Service Management API endpoints; complete details on Service Management API can be found on [ETSI Forge](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/011/02.02.01_60/gs_MEC011v020201p.pdf).'
  license:
    name: BSD-3-Clause
@@ -698,7 +699,8 @@ components:
          type: boolean
        livenessInterval:
          type: integer
          description: Interval (in seconds) between two consecutive "heartbeat" messages (see clause 8.2.10.3.3).
          description:
            Interval (in seconds) between two consecutive "heartbeat" messages (see clause 8.2.10.3.3).
            If the service-producing application supports sending "heartbeat" messages, it shall include this attribute in the registration request. In this case, the application shall either set the value of this attribute to zero or shall use this attribute to propose a non-zero positive value for the liveness interval.
            If the application has provided this attribute in the request and the MEC platform requires "heartbeat" messages, the MEC platform shall return this attribute value in the HTTP responses. The MEC platform may use the value proposed in the request or may choose a different value.
            If the MEC platform does not require "heartbeat" messages for this service instance it shall omit the attribute in responses.
@@ -1088,7 +1090,7 @@ components:
            $ref: '#/components/schemas/SerAvailabilityNotificationSubscription'
          example:
            subscriptionType: 'SerAvailabilityNotificationSubscription'
            callbackReference: "http://my.callback.com/mec_service_mgmt_ser_availabilities/some-id"
            callbackReference: 'http://my.callback.com/mec_service_mgmt_ser_availabilities/some-id'
            filteringCriteria:
              serNames:
                - 'myRnis'
@@ -1241,5 +1243,3 @@ components:
              - 'https://my.callback.com/sandboxname/rni/v2/'
        serializer: 'JSON'
        scopeOfLocality: 'MEC_SYSTEM'