circusfly

If the code in PROD was fine before the rollout, and there is a bug in the newly deployed code; then I was saying above to undo that deployment going back to the previous version then replicate the bug, preferably locally.

It seems like there a misunderstanding about what I wrote or there is a misunderstanding about how kube works and the misunderstanding isn't mine.

It burns purple too.

kubectl rollout undo deployment/foo then replicate. The article predates kube though.

If it can't be replicated, loop back to the reporter and seek any clarifying details. If that fails, then communicate to management the extremely high risk of attempting a fix.

I'm happy to get into a legacy Java stack and make it nice!

AI thanks you for your efforts.

> Apparently they encrypted customer passwords instead of one-way hashing [1].

Pretty incredible, I use one way hashing for my own sites and I don't even have customers, just a couple of accounts I use when I want to demo something.

I Googled "online gantt tool" and there are whole companies that do nothing but Gantt charts. Pretty wild.

I saw a job posting for Aha! which bills itself as #1 product development software. It seems to be a mashup of a Gantt chart, web forums, virtual sticky notes, document database and a Kanban looking board, and they mention "AI" near the bottom.

I'm not against it but the whole thing does look quite anti-Agile to me, which might not be a bad thing.

At the speed of the ISS, a very long time, pack tuna sandwiches.

Down voted for asking a valid question? Or is every reader of every HN post expected to be an in depth expert in every article posted every minute of every day of the year? What kind of asshole who has earned the right to down vote comments on HN would down vote a legitimate question?

Well, yes, I can, but unlike ssh which is open to the world, my VPN is only open to me and the family. It seems like that greatly reduces the potential attack surface.

Could the backdoor have targeted Wireguard instead of ssh?