@varkes/app-connector

@varkes/app-connector

npm i @varkes/app-connector

28 Versions

0.13.6

latest
7 months ago

loading event spec from local storage in case it is not attached to the remote API, respecting now also packages


0.13.5

7 months ago
  • loading event spec from local storage in case it is not attached to the remote API

0.13.4

8 months ago
  • UI support for cloud events
  • improved error handling when sending events in compass mode

0.13.3

1 year ago
  • Previous patch release were made partial only, updated versions in all modules proper now

0.13.1

1 year ago

0.13.0

1 year ago
  • Added support for cloud events in binary and structured mode
  • Extended UI to support cloud events in structured mode
  • Improved eventing logs

0.12.0

1 year ago
  • Renew certificates via API and UI
  • Fixed problem with downloading client key/cert in chrome

0.11.2

2 years ago
  • Improved request logs
  • Fixed missing support for urlencoded requests used in oauth/token endpoint
  • removed stress-mock from examples
  • updated dependencies
  • Fixed configuration option for request retries to info point
  • enabled non-colored json logs for docker deployments

0.11.1

2 years ago

0.11.0

2 years ago

Features

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

0.10.7

2 years ago

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)

0.10.6

3 years ago

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

0.10.5

3 years ago

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

0.10.4

3 years ago
Fixes
  • Update of dependencies
  • Configurable retry for connection establishment
  • Fixed printing logs multiple times

0.10.3

3 years ago
Features
  • Adjustments for the new packages API of compass
  • Added new healthz endpoint for readinessProbes

0.10.2

3 years ago
Features
  • Cockpit module gets released in production mode and with that gets served much more efficient

0.10.1

3 years ago
Features

0.10.0

3 years ago
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.

0.9.3

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

0.9.2

3 years ago
Features
  • Fixes certificate encoding problem (#264)

0.9.1

3 years ago
Features
  • Fix for odata API registration problems (#262)

0.9.0

3 years ago
Features
  • Support for Compass (#260)
  • Support for defining specifications as URLs (#243)
  • Removed unused feature of added_endpoints in config (#252)
  • More error handling (#254)
  • Support of AsyncAPI v2 (#255)
  • Update of dependencies (#259)

0.8.0

3 years ago
Features
  • Explicit resolving of configuration by changing signature of all modules to use config object
  • Icon and name of mock gets displayed in banner of cockpit
Usage

Use the modules as express middleware in your express based NodeJs application.

Depending on the modules you require, add the dependencies to your package.json like that:

  "dependencies": {
    "@varkes/configuration": "^0.8.0",
    "@varkes/api-server": "^0.8.0",
    "@varkes/odata-mock": "^0.8.0",
    "@varkes/openapi-mock": "^0.8.0",
    "@varkes/cockpit": "^0.8.0"
  }

In your application enable the modules in your express app like that:

const config = require("@varkes/configuration")
const odataMock = require("@varkes/odata-mock")
const openapiMock = require("@varkes/openapi-mock")
const server = require("@varkes/api-server")
const cockpit = require("@varkes/cockpit")
const app = require('express')()

let configuration = config.resolveFile("./varkes_config.json")
app.use(await odataMock.init(configuration))
app.use(await openapiMock.init(configuration))
app.use(await server.init(configuration))
app.use(await cockpit.init(configuration))

app.listen(10000, function () {
       console.info("Started application on port %d", 10000)
})

0.7.0

3 years ago
Features
  • Updated dependencies
  • New package @varkes/configuration unifying the configuration
Usage

Use the modules as express middleware in your express based NodeJs application.

Depending on the modules you require, add the dependencies to your package.json like that:

  "dependencies": {
    "@varkes/api-server": "^0.7.0",
    "@varkes/odata-mock": "^0.7.0",
    "@varkes/openapi-mock": "^0.7.0",
    "@varkes/cockpit": "^0.7.0"
  }

In your application enable the modules in your express app like that:

const odata = require("@varkes/odata-mock")
const openapi = require("@varkes/openapi-mock")
const server = require("@varkes/api-server")
const cockpit = require("@varkes/cockpit")
const app = require('express')()

app.use(await odata.init("./varkes_config.json"))
app.use(await openapi.init("./varkes_config.json"))
app.use(await server.init("./varkes_config.json"))
app.use(await cockpit.init())
app.listen(10000, function () {
       console.info("Started application on port %d", 10000)
})

0.6.3

3 years ago
Features
  • Updated dependencies
  • Fixed release process, all examples will have a docker image released
Usage

Use the modules as express middleware in your express based NodeJs application.

Depending on the modules you require, add the dependencies to your package.json like that:

  "dependencies": {
    "@varkes/api-server": "^0.6.3",
    "@varkes/odata-mock": "^0.6.3",
    "@varkes/openapi-mock": "^0.6.3",
    "@varkes/cockpit": "^0.6.3"
  }

In your application enable the modules in your express app like that:

const odata = require("@varkes/odata-mock")
const openapi = require("@varkes/openapi-mock")
const server = require("@varkes/api-server")
const cockpit = require("@varkes/cockpit")
const app = require('express')()

app.use(await odata.init("./varkes_config.json"))
app.use(await openapi.init("./varkes_config.json"))
app.use(await server.init("./varkes_config.json"))
app.use(await cockpit.init())
app.listen(10000, function () {
       console.info("Started application on port %d", 10000)
})

0.6.2

4 years ago
Features Usage

Use the modules as express middleware in your express based NodeJs application.

Depending on the modules you require, add the dependencies to your package.json like that:

  "dependencies": {
    "@varkes/api-server": "^0.6.2",
    "@varkes/odata-mock": "^0.6.2",
    "@varkes/openapi-mock": "^0.6.2",
    "@varkes/cockpit": "^0.6.2"
  }

In your application enable the modules in your express app like that:

const odata = require("@varkes/odata-mock")
const openapi = require("@varkes/openapi-mock")
const server = require("@varkes/api-server")
const cockpit = require("@varkes/cockpit")
const app = require('express')()

app.use(await odata.init("./varkes_config.json"))
app.use(await openapi.init("./varkes_config.json"))
app.use(await server.init("./varkes_config.json"))
app.use(await cockpit.init())
app.listen(10000, function () {
       console.info("Started application on port %d", 10000)
})

0.6.1

4 years ago
Features
  • Fixed a dependency issue in the new "api-server" module
  • General update of dependencies
Usage

Use the modules as express middleware in your express based NodeJs application.

Depending on the modules you require, add the dependencies to your package.json like that:

  "dependencies": {
    "@varkes/api-server": "^0.6.1",
    "@varkes/odata-mock": "^0.6.1",
    "@varkes/openapi-mock": "^0.6.1",
    "@varkes/cockpit": "^0.6.1"
  }

In your application enable the modules in your express app like that:

const odata = require("@varkes/odata-mock")
const openapi = require("@varkes/openapi-mock")
const server = require("@varkes/api-server")
const cockpit = require("@varkes/cockpit")
const app = require('express')()

app.use(await odata.init("./varkes_config.json"))
app.use(await openapi.init("./varkes_config.json"))
app.use(await server.init("./varkes_config.json"))
app.use(await cockpit.init())
app.listen(10000, function () {
       console.info("Started application on port %d", 10000)
})

0.6.0

4 years ago
Features
  • Extracted all kyma connection logic into a dedicated module "app-connector"
  • Renamed "app-connector-client" to "api-server"
  • Migrated api-server to typescript
  • Introduced "modules" folder for all varkes components
  • Updated documentation
  • switched to swagger-ui instead of using re-doc, benefit is a try-out feature
Usage

Use the modules as express middleware in your express based NodeJs application.

Depending on the modules you require, add the dependencies to your package.json like that:

  "dependencies": {
    "@varkes/api-server": "^0.6.0",
    "@varkes/odata-mock": "^0.6.0",
    "@varkes/openapi-mock": "^0.6.0",
    "@varkes/cockpit": "^0.6.0"
  }

In your application enable the modules in your express app like that:

const odata = require("@varkes/odata-mock")
const openapi = require("@varkes/openapi-mock")
const server = require("@varkes/api-server")
const cockpit = require("@varkes/cockpit")
const app = require('express')()

app.use(await odata.init("./varkes_config.json"))
app.use(await openapi.init("./varkes_config.json"))
app.use(await server.init("./varkes_config.json"))
app.use(await cockpit.init())
app.listen(10000, function () {
       console.info("Started application on port %d", 10000)
})

28 Versions

TagPublished
0.13.6latest7mos ago
0.13.57mos ago
0.13.48mos ago
0.13.31yr ago
0.13.11yr ago
0.13.01yr ago
0.12.01yr ago
0.11.22yrs ago
0.11.12yrs ago
0.11.02yrs ago
0.10.72yrs ago
0.10.63yrs ago
0.10.53yrs ago
0.10.43yrs ago
0.10.33yrs ago
0.10.23yrs ago
0.10.13yrs ago
0.10.03yrs ago
0.9.33yrs ago
0.9.23yrs ago
0.9.13yrs ago
0.9.03yrs ago
0.8.03yrs ago
0.7.03yrs ago
0.6.33yrs ago
0.6.24yrs ago
0.6.14yrs ago
0.6.04yrs ago