Require Service Type Config (#322)

* Require configuration for each service #318
* Made parameters required in file_formats and service_types #318

CHANGELOG.md

@@ -17,10 +17,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - `GET /collections/{collection_id}`: Added optional `assets` property for collection-level assets. This may link to visualizations for example. [#211](https://github.com/Open-EO/openeo-api/issues/211)
 - `GET /collections`, `GET /jobs`, `GET /process_graphs`, `GET /Services`: Allow all non-scalar properties to be part of the response although strongly discouraged.
 
-### Changes
+### Changed
 - `GET /credentials/oidc`: field `scopes` is not required anymore, but when specified, it should contain the `openid` scope. [#288](https://github.com/Open-EO/openeo-api/pull/288)
 - `GET /.well-known/openeo` and `GET /`: `production` fields default to `false` instead of `true`.
 - `GET /jobs/{job_id}/logs` and `GET /services/{service_id}/logs`: `path` property is not required any longer. [#320](https://github.com/Open-EO/openeo-api/issues/320)
+- `GET /file_formats`: `parameters` is now required for each file format. [#318](https://github.com/Open-EO/openeo-api/issues/318)
+- `GET /service_types`: `configuration` and `process_parameters` are now required for each service. [#318](https://github.com/Open-EO/openeo-api/issues/318)
 - `GET /service_types` and `GET /file_formats`:
     - Allow full JSON Schema for parameters, instead of a very limited subset.
     - Instead of the proprietary property `example` use `examples` from JSON Schema instead.

openapi.yaml

@@ -2233,6 +2233,9 @@ paths:
                   x-additionalPropertiesName: Service Name
                   title: Service Type
                   type: object
+                  required:
+                    - configuration
+                    - process_parameters
                   properties:
                     title:
                       $ref: '#/components/schemas/object_title'
@@ -2299,8 +2302,7 @@ paths:
                       title: OGC Web Map Service Standard
                 OGCAPI-FEATURES:
                   title: OGC API - Features
-                  description: >-
-                    Exposes a OGC API - Features in version 1.0 of the specification (successor of OGC WFS 3.0).
+                  description: Exposes a OGC API - Features in version 1.0 of the specification (successor of OGC WFS 3.0).
                   configuration:
                     title:
                       type: string
@@ -2310,7 +2312,7 @@ paths:
                       description: The description for the OGC API - Features landing page
                     conformsTo:
                       type: array
-                      description: >-
+                      description: |-
                         The OGC API - Features conformance classes to enable for this service.
 
                         `http://www.opengis.net/spec/ogcapi-features-1/1.0/conf/core` is always enabled.
@@ -2321,6 +2323,7 @@ paths:
                           - http://www.opengis.net/spec/ogcapi-features-1/1.0/conf/html
                           - http://www.opengis.net/spec/ogcapi-features-1/1.0/conf/geojson
                           - http://www.opengis.net/spec/ogcapi-features-2/1.0/conf/crs
+                  process_parameters: []
                   links:
                     - href: 'https://www.opengeospatial.org/standards/wfs'
                       rel: about
@@ -3586,6 +3589,7 @@ components:
       description: Describes a specific file format.
       required:
         - gis_data_types
+        - parameters
       properties:
         title:
           $ref: '#/components/schemas/object_title'