remram

I invite you to re-read the second paragraph of my post.

You’re just throwing things I already listed back at me. I mentioned a staging environment, I mentioned a schedule was a (bad) option.

Maybe I’m not being clear.

I want to stagger updates, giving time to make sure they work before they hit the whole fleet.

If a new SSH version comes out on Tuesday, I want it installed to 1/3 of the machines on Tuesday, another third on Wednesday, and the rest in Friday. Or similar.

Having machines update on a schedule means I have much less frequent updates and doesn’t even guarantee that they hit the staging environment first (what if they’re released just before the prod update time?)

Probably not. Obfuscation works, and might even depend on remote code being downloaded at either build time or run time.

There are a lot of heuristics you can use (e.g. disallowing some functions/modules) to check a codebase, but those already exist no AI required. Unless you call static analysis “AI”, who knows.

Is there anything about staggered upgrades and staging environments in there? Because obviously I had read it before posting…

If you’re one of those people that think every product is better if there’s “AI” on the box then sure. What you’re describing is static analysis though, it is not new.

Did it write that playbook? Did you read it?

So you can test the updates before fixing production.

My question is how to do that with APT.

I don’t know, I recently got a 2-in-1 laptop, and was surprised to see that KDE works great. Got Onboard as on-screen keyboard. Screen rotation works great. Glad I didn’t have to run Gnome on that machine.

Exactly this. Services and software are not the same thing, you’re asking for a service recommendation and it can’t be open-source software because it’s not software.

What was “the point”? From my perspective, I had to correct a fifth post about using a schedule, even though I had already mentioned it in my post as a bad option. And instead of correcting someone, turns out I was replying to a bot answer. That kind of sucks, ngl.