Skip to content

IRIS Ops Studio 1.1.0 — Verifiable Operations

Choose a tag to compare

View all tags
@seypherWork seypherWork released this 22 Sep 22:15
· 6 commits to main since this release
v1.1.0
0350b7a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

IRIS Ops Studio 1.1.0 adds verifiable administration workflows to the original safety-first console for InterSystems IRIS Community 2026.2.

New since 1.0.0

  • Preview → confirm → execute → readback: guided process, task, user-role, and role-resource changes show the expected result and report whether a fresh read actually matches it. Pending, mismatched, blocked, and unverified outcomes are distinguished from verified changes.
  • Safer access changes: user-role and role-resource plans preserve unrelated settings, send only documented mutable fields, and block a stale preview before PUT.
  • Incident Timeline: one filtered view of IRIS audit records, task history, and this browser session's operation journal, with source, severity, entity, actor, text, and correlation filters.
  • Broader, more honest exploration: 34 SysAdmin API v2 method/path pairs catalogued (27 in 1.0.0), simulated demo results clearly labelled, unsupported demo requests declined, and sensitive fields and credential-shaped text redacted before display.
  • Deployment and usability: durable IRIS container data, Node.js 22/24 CI, and responsive desktop/mobile layout checks.
  • Updated product tour: three new Safe demo screenshots show Incident Timeline and the process/access preflight dialogs. The earlier overview video is labelled as such.

Verification

57 automated tests pass. The four testable API, explorer, operation, and sanitization modules reached 98.98% aggregate line coverage in the final local run; this is not whole-application coverage. Selected guided workflows and authenticated reads were checked on disposable IRIS Community 2026.2 instances. See the validation report for exact evidence and limits.

Try it

  • Safe public demo — no IRIS account required; changes are simulated.
  • Run npm start for the local demo, or docker compose up --build to install into the provided disposable IRIS stack.

Security boundary: previews, confirmations, and journaling are browser-side operator safeguards. IRIS authorization remains the server-side enforcement point. This release does not implement server-enforced per-tab read-only mode, a complete dependency graph, or an all-source IRIS log stream. The existing video documents the original overview; it does not yet show the new 1.1.0 workflows.

Assets 2
Loading