Varkes 0.10.0

Features

• Improved usability by reducing the amount of configuration efforts (#267)
  • the basepath is optional - if not specified the basepath from api spec gets used
  • provider on root level - the "provider" attribute cannot be configured per api anymore, instead it is on root level as it will be the same for all api entries usually
  • New root level attribute "application" - it turned out that the name of the actual application to be mocked is useful as prefix for every API name. If the "application" attribute is specified, all api names will be prefixed with it. If no root "name" is specified, the "name" will be the "application" + " Mock"
  • The root "name" gets optional as it can be configured by "application"
  • The API type will be derived from the specification file type, if not configured explicitly
  • Any basepath can be configured for odata APIs. The corresponding REST API will be exposed via /api + basepath from now
  • Fixed: the "Console" link in the console was not working for ODATA APIs.
    the odata-mock supports ".edmx" file extensions as well
  • Kubernetes 1.16 support for all the deployment files

Breaking Changes

• The 'provider' attribute in the configuration of each API or Event API moved to the root of the configuration
• The ODATA mock had a requirement to contain an /odata/ path as part of the basepath. This static basepath element was used to offer the related REST API by replacing it with api. As this requirement was too demanding, the REST API will now be served by a basepath prefix /api. The effect is that any basepath will be supported. To access the REST API just prefix it. The downside is that the URL to the REST API has changed.