Sidehistorik
...
DevOps and Continues Delivery concepts extending the traditional concepts of the traditional Developer vs. Sysadmin thinkingapproach, where a common stage sence is that Sysadmins deploys, while Developers does not interact with Stage- or Production-environments.
These are not nesesarily colliding necessarily colliding ways of thinking, but requires some thinking and implementation that enforces special rules and approval-procedures, since (learned over 10 years as Sysadmin):
| Info |
|---|
The Developers Point Of View on classic vertues virtues and procedures are typically focused in a complete other direction than those of the Sysadmin - The Developer has a focus on getting quickly to the next finish line with features and deployment - sometimes the cost are giving a little slack on test and deployment diciplin. Giving the Developer access to Deployment in the Stage or Production without enforcing special rules and approval-procedures, do consider the battle lost |
...
| Advarsel |
|---|
Do also give data confidentiallity confidentiality and data security a thought, when Developers are given any form of access to Stage or Prod, as these environments often contains confidential or classified content; just by giving Developers access, the numbers of people with possible access rises, secondly because the Developer [potentially] has the possibility to use the software to extract confidential or classified informations more directly. One of the developers common reasons to require Stage or Production access is the need for debug or log informations, here I do recommend using a facility like splunk for collecting data (in a controlled manner) off the servers/systems.
Also, seperation separation of dutys duties are often a requirement for IT-Revision and data security/control |
Environments
The minimum should be:
...