#Tag

Posts tagged "automation"

← All posts

  1. The form supplied defaults my script never sent

    Create an OAuth2 provider through Authentik's admin form and logins work; create it in the admin shell and every login comes back as a malformed request, because the form was ticking boxes the model leaves empty. Automation that writes underneath a form inherits the form's job, and a working object shows what that job includes without deciding it for the next app.

  2. A health check cannot prove a reboot happened

    Automation that confirms a restart by polling for a healthy API is asking a question the old boot answers just as cheerfully as the new one. Gate a transition on evidence only the new state can produce: for a reboot, a boot ID that differs from the one you recorded before the change.

  3. A finished scan can have walked nothing

    A library scan answered 200 and its scanner logged a launch and a finish about eighty milliseconds apart with zero files found, because one parameter was an empty array where a folder path belonged. The tool had done exactly what it was asked. Only an inventory taken outside it, set against its own records, showed two libraries 164 files short.

  4. If your automation opens an SSH session, it isn't automation

    A play that opens a shell and greps the output is screen-scraping with a schedule attached, and it reports changed on every run because it has no idea whether it changed anything. The same work rebuilt against a typed API buys idempotency, a real preview and a change count you can believe.

  5. Every build succeeded. The dashboard said they all failed.

    A CI runner executed flawlessly for a month - images pushed, deploy branches landed - while reporting failure to the dashboard every time. A three-post release sat stranded for a fortnight because the status was believed over the artefacts.

  6. Consistency by construction beats consistency by discipline

    One address had to appear in the application config, the network attachment and two policy objects - four artefacts, four update paths. Rendering every one of them from a single required value made divergence something the tooling can no longer express.