Prod deployments should come from a build server though and if you're deploying multiple times a day you should have a well built CI pipeline to handle it.

Remoting into a management server would still have people using an account on the management server and their personal db login credentials.

We also don't give devs write access to production and all scripts run in production are run by our DBA after they have been approved by the lead Dev, operations and the DBA.

This might be overkill for some systems, but we won't ever accidentally delete our prod data. Our system requires this level of scrutiny due to the nature of our systems.

[–] zalgotext@sh.itjust.works 3 points 1 day ago (1 children)

Sure, that's a very, very robust way of doing things. And I'm not trying to say what you're describing is wrong either. I'm just saying that some places don't have the knowledge/ability to set things up that way, so they play fast and loose with prod access. Couple that with giving LLMs free reign over the computer with those prod settings, and you end up in situations like in the original post.

It's not unrealistic, is all I'm trying to claim. It's a failure on several levels, but it's not unrealistic.

[–] Zannsolo@lemmy.world 1 points 21 hours ago (1 children)

I didn't say it was unrealistic it's just stupid. I have no doubt thousands of companies are not practicing good access controls to a production db, but it's not smart as seen by this post.

[–] zalgotext@sh.itjust.works 1 points 21 hours ago

I... Yeah, I just said pretty much the same thing lol