Fixing a finding
| From | The finding of the nightly run |
| Who | You, in the morning |
| Your part | One click, one sentence, one approval |
| Level | rw- Asks before changes, see the three levels |
Problem
The nightly run from the recipe Security updates every night left two security updates on web07 alone because the journal demanded it. Now a finding stands on the list. Somebody would have to read up why the packages were held back in March, whether the reason still holds, and then decide. Exactly the kind of task that sits for weeks.
Wanted: a decision the same morning, without searching changelogs yourself.
Solution
One click turns the finding into a session. Heinzel Pro reads up, proposes two ways, you decide.
Step 1: You open the finding
The findings page collects what the nightly runs were not allowed to decide alone, with a severity and a proposal of what to do. One click on "Open a new session to fix it", nothing to type.
Step 2: The session is prepared
Server, task and the finding are already in place. The level stays at "Asks before changes", because this time a person is to decide. You start.
Step 3: Heinzel Pro reads up and proposes two ways
It finds in the application's changelog why the update went wrong in March, and that the reason has been fixed since May. Then two ways: update the two packages today, or move the application to PHP 8.3. It recommends the first and waits.
Step 4: You answer and approve
Input: First way. Please record the second as a finding so we tackle it next month.
Heinzel Pro updates, restarts the service, checks the application's login page and writes the journal. The night's finding is closed, and the new one stands on the list with your sentence, for next month.
