6d0b817b2cd31abfe4a8fa0fd0998e33c93d4c7f
L2 of the PocketBase->Postgres migration (bead archie-core-7r0x.3): a new Postgres-backed EDA adapter (postgres.EDA) plus its goose migration (0002_edastore.sql) and sqlc queries (queries/edastore.sql), satisfying the same storecontract surfaces as internal/infrastructure/edastore.Store so the cutover wave can swap them behind the contract. The PocketBase opener in internal/app/archied/state_store.go is untouched: production still opens SQLite, and the cutover waits for the one-time import. Three recon-found hazards, each pinned by a test, not a comment: 1. Empty-secret early return. applyBinding deliberately never writes the secret column when the incoming secret is empty, so an edit form that does not echo the secret must not blank an armed binding's HMAC key. The UpdateBinding query keeps the stored secret via `secret = CASE WHEN $secret = '' THEN secret ELSE $secret END`; pinned by TestUpdateBindingEmptySecretPreservesStored (raw column unchanged across an empty-secret edit). 2. Unique-violation detection by SQLSTATE. isUniqueViolation previously grepped the driver's error text for "unique"/"already exists"; Postgres reports SQLSTATE 23505 and the text match would not fire, losing ErrAlreadyDispatched. The adapter detects by pgconn.PgError.Code == "23505"; pinned by TestIsUniqueViolationDetectsBySQLState (23505 with a message lacking those words is detected; a non-23505 whose text says "unique" is not). 3. One-binding-per-source / one-armed-binding-per-source were read-then-refuse with no transaction and a non-unique idx_bindings_source_status. Made them constraints: UNIQUE(source) plus a partial UNIQUE(source) WHERE status='armed' (the full unique subsumes the armed rule today, kept explicit for a future matcher extension). A concurrent insert for one source yields exactly one success and one ErrBindingOverlap; pinned by TestConcurrentInsertBindingSameSource. Dispatch ledgers kept exactly: UNIQUE(binding, capture) and UNIQUE(playbook_id, playbook_version, event_id, action_id); binding_version is stored but deliberately not part of the key (pinned by TestBindingDispatchVersionBumpDoesNotPermitRedispatch). The cipher is unchanged: AES-256-GCM, key = SHA-256(material), decrypt stays in the store and the gRPC wire still carries plaintext. Notify is left as an injected callback (EDA.SetNotify) and is NOT wired to LISTEN/NOTIFY. It is dead code today: edastore.Config.Notify is omitted at its only production construction and no consumer maps binding_changed/ mapping_changed, so building a LISTEN/NOTIFY path would be building for a consumer that does not exist. Wired or not is a separate decision.
Description
Archie connects events from your systems to agents that can investigate, reason, and act.
Define what an event means, map its data into a workflow, and give that workflow an agent equipped for the job: its own execution environment, tools, and identity.
https://archie.catlow.cloud
133 MiB
0 Stars
1 Watchers
0 Forks
Releases
11
Archie v1.62.0
Latest
Languages
Go
76.8%
Vue
13.1%
TypeScript
7.8%
JavaScript
1.2%
Shell
0.6%
Other
0.4%