Code is deployed in containers. Improved capabilities to debug those systems will be really helpful to me (and I'm sure many others). Recreating real-world state locally takes effort and is error prone
Code is deployed in containers. Improved capabilities to debug those systems will be really helpful to me (and I'm sure many others). Recreating real-world state locally takes effort and is error prone
As I said, you can either have better, cleaner architecture where the fact it's deployed to containers does not matter; or, you could decide not to deploy to containers if you are going to be breaking container boundaries in production systems anyway!
It's a pretty big cognitive dissonance to me: we move away from direct access to increase our security posture, and then put more effort to break the barriers we just put in. Next, we'll put more effort in to harden these backdoors, break them again to be more productive...
In most orgs that follow relevant secure development lifecycle standards and legislation, engineers usually won't be able to do that for legal reasons anyway (due to GDPR or CRA in EU; comparable laws in California or New York), so really, big orgs will require you to not debug live production system but log relevant information, and act upon it later.
Anyway, we are all bound to re-learn these lessons, so good luck to anyone entering the scene today :)