Varkes 0.11.0

Features

• Certificate renewal on expiration (#287)
• updated dependencies (#288)

Varkes 0.10.7

Features

• Cockpit: bringing back the "connected" status button (#280)
• Cockpit: added toggle to send event with trace sampling active (#282)
• Cockpit: fixed console links when referer header had trailing slashes (#284)

Varkes 0.10.6

Features

• Cockpit: displaying a loading spinner to the connection process (#277)
• api-connector: removed domain info from connection state as it was unused (#278)
• api-connector: retrieve the eventURL for every event request to support dynamic flavor in compass legacy connector (#278)
• api-server: fixed a bug in resolving the api name
• api-server: added REFER header as an alternative to the ORIGIN header to resolve original requester URL

Varkes 0.10.5

Features

• Fixed API registration problem with latest Compass version, defaultAuth attribute moved to package level
• API Names will not be prefixed anymore with the application name in case of a compass connection

Varkes 0.10.4

Fixes

• Update of dependencies
• Configurable retry for connection establishment
• Fixed printing logs multiple times

Varkes 0.10.3

Features

• Adjustments for the new packages API of compass
• Added new healthz endpoint for readinessProbes

Varkes 0.10.2

Features

• Cockpit module gets released in production mode and with that gets served much more efficient

Varkes 0.10.1

Features

• Removed API specifications from any collection API getter => improved UI responsiveness (#269)
• Used dedicated "varkes" attribute in API registration payloads to have varkes specific metadata available in UI. Before the "labels" were misused and with that were displayed in kyma serviceCatalog (#269)

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.

Varkes 0.9.3

Features

• Adds retry logic to connection flow in order to make it more robust (#265)