271e03d8205af4b1a765cb6c634779707ebfcd1f
The version committed in the previous commit was authored blind, without knowing a real archie-update-check already existed and has been running on carina (production) since Aug 9 -- just never committed to the repo. That live version is better designed than what I wrote: it introspects the actually-running binary via `archied -version` rather than trusting git/filesystem state that could have silently diverged from what's really installed, and uses `git ls-remote` for the available version instead of a local fetch, so the script has no side effects and no dependency on the checkout being a buildable Go workspace. Adopt it as the canonical version, with one real fix: it used Component IDs "archied"/"archie-agent", which don't match releaseupdate.ComponentDaemon="daemon"/ComponentAgent="agent" -- the same convention archie-update-watchdog's report and this session's Service.Enrich already use. Under the old IDs, neither ever actually applied to carina's real update checks; the mismatch was silent since an unrecognised component ID just leaves InstallType/Reference/ Verify() unset rather than erroring.
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%