v2.26.0

Highlights

CloudTrail is the story of this release. The browser failed every fetch on many accounts, its filters had to be typed from memory, and combining two of them quietly returned the wrong rows. All three are fixed, and reading a long window no longer means waiting for it.

CloudTrail

• The browser failed every fetch on some accounts. Event resource entries do not always carry a type, and the parser assumed they did, so a single such event ended the fetch with an error and an empty table. AssumeRole events from instance profiles have exactly that shape, which makes this common on any account using instance roles or Systems Manager.
• Filters are pickers now. Event, user and resource type are built from the events you fetched, each option showing how many times it occurs, sorted by frequency. Choosing one narrows what is on screen immediately. Each picker also offers to type a value, for something further back in the window than the events you have loaded; a typed value is searched for across the whole range.
• Combining filters used to lie. The lookup API honours only the first filter you send and silently ignores the rest, so asking for an event name and a user returned rows matching just one of them. Filters are now applied faithfully, and they combine, which the API on its own cannot do. This applies to the agent tool as well.
• Reading on. The fetch stops at a cap so it stays fast, but Next now reads the next page instead of going dead at the end, about two seconds for another 500 events, and everything you load joins the pickers. The cap default is 500, and an existing config is migrated from the old 100 on first launch, keeping a backup. A number you chose yourself is left alone.
• Machine names instead of hex. An instance-role session is named after the instance id, so the user column read as a wall of identifiers. An id Servonaut recognises now shows the instance's name; filtering still works on the id behind it.

Demo mode

• The AWS launch wizard, the IP Ban screen and CloudTrail no longer show real key-pair names, security-group names, ban-configuration names or instance ids while demo mode is on.
• A scripted chat conversation can be replayed instead of calling the AI gateway, for recordings and offline demos. See docs/demo-mode.md.

Also fixed

• The log viewer honours a server's memory opt-out when choosing which log to open first, instead of using the cached list.

Upgrade with pipx upgrade servonaut. Your configuration is migrated automatically on first launch, and the previous file is kept alongside it.

What's Changed

• fix: log viewer honours memory opt-outs when choosing its first log by @zoltanam in #100
• feat: demo mode can replay a scripted chat conversation by @zoltanam in #101
• fix: CloudTrail browser failures and demo-mode gaps in the AWS screens by @zoltanam in #102
• feat: CloudTrail filters you can pick or type, paging that keeps going, and combining that no longer lies by @zoltanam in #103

Full Changelog: v2.25.4...v2.26.0