Chronacta Connector
Это содержимое пока не доступно на вашем языке.
Managed durable subscription runner with NATS-style reconnect via pkg/client/resilience.
Binary
Section titled “Binary”make build./bin/chronacta-connector -config connector.yamlConfiguration
Section titled “Configuration”See examples/connector-test/connector.yaml.
| Field | Description |
|---|---|
chronacta.address |
gRPC server address |
chronacta.token_env |
env var with bearer token |
jobs[].handler |
http or go:StructuredLog / go:NoOp |
jobs[].type |
durable (pull/ack loop) |
Handlers
Section titled “Handlers”- HTTP: POST JSON event; optional HMAC in
X-Chronacta-Signaturewhenhttp.secret_envset. - Go handlers: register at compile time with
connector.Registerin a custommainfork. go:PostgresReadModel: projects events into Postgres using a YAML read-model schema (postgres.schema+postgres.dsn_env). Apply DDL fromchronacta sqlgen generate ddlbefore starting. See postgres-projections.md andexamples/postgres-projector/.
Idempotency
Section titled “Idempotency”HTTP receivers must deduplicate by event_id. Delivery is at-least-once.
PostgresReadModel uses processed_events + UPSERT and ACKs only after a successful commit.

