Also, government regulations such as HIPAA explicitily force you to have separation of duties, so true DevOps is against them. Developer being able to push their code to production can earn you some hefty fine at the next audit.
Re:The Big DevOps Misunderstanding
by sethammons on Sunday December 19, 2021 @06:38PM
(#29619793)
We pass our audits all day long and I can push to prod multiple times a day. But there are caveats. Another developer must sign off on a code review and quality check before code rolled out, and a build pipeline ensures that we run our test suites and all changes have an audit trail.
Software is never done. It can only be abandoned.
There are projects that change slowly but they do change nonetheless unless they are no longer used.
Re:The Big DevOps Misunderstanding
by throwDec19 on Sunday December 19, 2021 @04:17PM
(#29618514)
We get heavily clamped down on access to production by our auditors for Sarbane Oxley reason. Technically we aren't even allowed production data in our dev environment. I dont understand why any organization would allow it. Seems the tech world is still ripe to get sued.
Re:The Big DevOps Misunderstanding
by KptMarchewa on Monday December 20, 2021 @05:17AM
(#29623103)
Because most of the world (also, as in industries) isn't under those type of laws.
Re:The Big DevOps Misunderstanding
by throwawayboise on Sunday December 19, 2021 @05:10PM
(#29618951)
Organizations did (do?) allow it because it's easy. It's also a way to test/debug production problems with actual production data instead of spending time trying to make up data that you hope covers all the actual use cases.
While I do like that definition, it also means that most companies/organisation cannot do DevOps, as software development is often bought as projects, and operations is a recurring cost.