Environment files

One file per environment in environments/. The filename without its extension becomes the environment name. Files are watched, so saving one reloads that environment within a second.

{
  "ConnectionStrings": {
    "PrimaryDatabase": "Server=sql.example.com;Database=PrimaryDB;Trusted_Connection=True;"
  },
  "ChangeTracking": {
    "PollingIntervalSeconds": 30,
    "ExportToFile": true,
    "FilePath": "exports/{environment}/{object}/changes-{timestamp}.json",
    "ExportToApi": false,
    "RetryCount": 3,
    "RetryDelaySeconds": 5,
    "TrackingObjects": [],
    "ApiEndpoints": []
  }
}

ConnectionStrings ​

A map of key to SQL Server connection string. Keys are referenced by TrackingObjects[].Database.

Values are encrypted in place on first read. Trignis sets Application Name=Trignis, and unless the string already specifies Packet Size, raises it to 32768 with a 30 second connect timeout for large payloads.

ChangeTracking ​

Every key here is optional. Omitted, it falls back to global settings.

TrackingObjects ​

{
  "Name": "Items",
  "Database": "PrimaryDatabase",
  "TableName": "dbo.Items",
  "StoredProcedureName": "web.get_itemssync",
  "InitialSyncMode": "Incremental"
}

InitialSyncMode only applies when no version is stored yet, which means first run or after a reset:

• Incremental adopts the current version and exports nothing. Only later changes are sent.
• Full exports every row, then continues incrementally.

ApiEndpoints ​

An HTTP endpoint:

{
  "Key": "webhook",
  "Url": "https://api.example.com/changes",
  "Auth": { "Type": "Bearer", "Token": "..." },
  "CustomHeaders": { "X-Correlation-Id": "{guid}" },
  "EnableCompression": false
}

A queue endpoint, distinguished by MessageQueueType:

{
  "Key": "rabbit",
  "MessageQueueType": "RabbitMQ",
  "MessageQueue": { "HostName": "localhost", "QueueName": "changes" }
}

Every endpoint receives every change in the environment. There is no per-object routing; separate environments if you need that.

Placeholders ​

Valid in FilePath, Url and CustomHeaders:

Validation ​

Configuration is validated at startup. Errors stop the service; warnings are logged and it continues. Common errors: a Database with no matching connection string, a missing StoredProcedureName, a queue endpoint with no MessageQueue, an unknown MessageQueueType.