Repository navigation
v0.0.12 fixes the restore defect behind caltechauthors issue #185 and adds a health check for RDM's log indices. A restore with include_global_state:false carries neither index templates nor data-stream definitions, so the app auto-created plain, text-mapped audit-log and job-logs indices and the admin audit-logs page silently stopped updating (HTTP 200, _shards.failed:1).
Three new forms under clasm rdm-backup-and-restore <slug> (RDM menu items 6, 7 and 8), each with -text|-json and -wait (default 5m, 0 checks once). rdm-index-health is a read-only check of the audit log and job logs: exit 0 healthy, 1 a problem (missing template, plain or orphaned log index, text mappings, failed shards, a plain index that a data-stream template claims). install-index-templates installs the templates the app would install, only the missing ones, through the app's own routine; it never overwrites, and a run with nothing missing exits 0 (DR-0199). convert-log-indices turns orphaned and plain log indices back into real data streams, copying first; it needs --confirm on a production instance (DR-0180). Copies are named clasm-fix-* and clasm never deletes them.
Restore OpenSearch (menu and command line) now ends with the install, the conversion and the health check, after the verified restore and the snapshot cleanup, with no second confirmation (DR-0199). The check's verdict is the restore's: a restore whose health check fails exits 1. Log indices are found by what they are, not by the alias, which a live restore of a pre-repair snapshot showed to matter. Verified live on a test instance.
Snapshots taken from a real data stream restore as a real data stream; older snapshots hold the orphan form, so the conversion stays.
Full Changelog: v0.0.11...v0.0.12