4 ms·
Separating config from code or separating declarative environments from orchestration of components aren't to satisfy your ops team standards, they're things yo
by Terretta 10y ago
Separating config from code or separating declarative environments from orchestration of components aren't to satisfy your ops team standards, they're things you probably want to do as a developer thinking of infra as code.
Also, DevOps: It doesn't mean same person doing all things, but it does mean you don't think in us vs. them.
Think about your app/service cradle to grave, do the right thing.
- ajamesm 10y agoAs a developer, I'm trying to meet deadlines with good-enough code. I'm not stupid and I certainly understand why someone would develop a general deployment strategy, and then each case can be described as a set of parameters. Again: the use case is clear to me. All of this makes sense in a world where the ops team is world-class and responsive, and you have the schedule and resources to delay deployment for another 2 weeks while you lovingly craft an Ansible module instead of hardcoding a BASH script. That does not describe business environments.