ost-skg-if-api-tools 0.1.3

This project merges multiple OpenAPI specifications extensions into a single core specification for SKG IF.

OpenAPI merge spec

Specify what should be changed in/added to the SKG-IF OpenAPI YAML, which supports the core SKG-IF data model, for an extension. RThis document will use an example server extension.

Header

Identify the extension. Potentially specify which extension(s) it extends and should already have been merged in the core OpenAPI YAML.

extension: service
# depends-on: foo
# depends-on: bar
skg-if-api:

Add tags

Add one or more tags. Each tag key, e.g. tag-service, should be unique. The + prefix tells the merger to add the tag.

  +tag-service:
    name: Service
    description: Lorem ipsum dolor sit amet. 
  #+tag-another:

Add schemas

Add one or more schemas. Each schema key, e.g. path-service, should be unique. The + prefix tells the merger to add the schema.

  +path-service:
    '/services/{local_identifier}':
      get:
        tags:
            - Service
  ...
  +path-services:
    '/services':
      get:
        tags:
            - Service
  ...

Modify a schema

Modify an existing (core) schema. Add the ~ prefix to the key of the schema to modify. Then copy all the steps that are needed to get to where a field has to be added or modified. In the example below its up to properties, to which services is added indicated by the + prefix. To step into the right item of a list the right position can be achieved with empty - items. The ~enum showcases a modification of its value list, i.e. adding the portal value.

~schema-venue:
    Venue:
      allOf:
        -
        - type: object
          properties:
            type:
              ~enum: portal
            +services:
              type: array
              items:
                $ref: '#/components/schemas/Service'