Pre-provision a tenants network connector

A single network connector can be configured through the tenant’s configuration file. The following block defines the network connector:

YAML

engine:
  network_connector:
    name: {{ Network Connector's Name }}
    type: {{ One of supported type. Officially supported types: loriot, chirpstack }}
    config:
      // Config Specific to the network connector

Example Configurations

Loriot

YAML

engine:
  network_connector:
    name: Thingshub Configured Loriot NC
    type: loriot
    config:
      server: https://eu4pro.loriot.io
      app_id: BEX422
      api_key: ApiKeyThatIsConfiguredInLoriot

Chirpstack

YAML

engine:
  network_connector:
    name: Thingshub Configured Chirpstack NC
    type: chirpstack
    config:
      host: https://chirpstack.example.com:443
      app_id: BEX422
      api_key: ApiKeyThatIsConfiguredInChirpstack
      accept_insecure_tls: true

The configuration option is officially supported for loriot and chirpstack only.

Runtime Behavior

When a network connector is configured through the tenant’s configuration file:

If the network connector of the provided type already exists:
- It is updated with the provided configuration
  - If it can’t be updated:
    - The engine service crashes
If the network connector of the provided type does not exist:
- If the network connector of a different type is configured previously
  - It is deleted
    - If it can’t be deleted:
      - The engine service crashes
  - The new network connector is created
    - If it can’t be created:
      - The engine service crashes
- If no network connector is configured previously:
  - The new network connector is created
    - If it can’t be created:
      - The engine service crashes

Please check the error details on the logs to identify which of the above scenarios is causing the engine service to crash, and resolve it accordingly.