6 ms·
Okay, except I was already writing Python scripts to deploy, so now I'm where I started off except I have one additional engineer yelling at me for not doing th
by ajamesm 10y ago
Okay, except I was already writing Python scripts to deploy, so now I'm where I started off except I have one additional engineer yelling at me for not doing things The Ansible Way.
This is the exact problem the article was describing -- CM tools promise ease-of-use and simplicity, then that premise is inverted entirely when the developer is now doing additional work to satisfy the operations team's standards.
- Terretta 10y agoSeparating 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.