v0.6.46: Runs that explain themselves
A run that cannot start now says why within minutes, test details show Maester's own description and result, the Tests pages agree with Changes, and the portal tells you when a newer release is out.
What’s new
- A run that cannot start now says why. If the runner never checks in, the run stops after about ten minutes instead of running into the two-hour limit, and its console shows what Azure’s own diagnostics for the runner job reported, such as an image that could not be pulled. A runner that cannot get its managed identity token, or whose check-in your deployment refuses, fails within a few minutes with the reason in the portal.
- Test details from Maester’s own report. Each test shows the description and result Maester wrote, including tables and nested steps, and skipped or errored tests show their reason. Very long details are trimmed at 30,000 characters with a note. Runs recorded before you update don’t have these details; every run after it does.
- Know when a new release is out. Your instance checks the public release list at maester.cloud every six hours and shows a banner when a newer release is available. Owners and Admins get an Update button that opens the setup site. The check sends no identifiers, and an Owner or Admin can turn it off under Settings > Deployment.
- Troubleshooting logs you control. When support needs more than a failure code, an Owner can share run consoles and the app’s log from Settings > Troubleshooting logs for 1, 3 or 7 days. Sharing is off by default, turns itself off, and every change is recorded in your access audit. These logs can contain tenant and test details; tokens and secrets are removed before anything leaves your deployment.
Fixes
- The Tests page and each test’s detail page compare the same two runs per tenant as Changes, so the three views agree about what drifted.
- A test’s detail page follows the tenant picker instead of mixing in other tenants’ results.
- When a run’s results cannot be loaded, the Tests page says so and offers Retry, instead of silently leaving that run out.
- Fixed intermittent errors when opening the portal and loading results, caused by two requests updating the same “last seen” time at once.
- If the runner cannot sign in to Azure, the run continues and skips only Maester’s Azure checks, and the console says so.
- The setup wizard’s Permissions page shows the Exchange Online logo.
How to update
- Open setup.maester.cloud and sign in with the account you used for setup.
- Choose your instance and select Update. The update applies in place, and your stored results and history are untouched. No new permissions or consent are needed.
- From this release on, the portal tells you when the next one is out.
If you run setup from PowerShell, update the module first with Update-Module MaesterCloud -AllowPrerelease, then run Start-MaesterCloudSetup.