4 ms·
> and no amount of Ansible/SaltStack/Puppet script will save you from this. And I am afrade you missed my point entirely if you are bring up yet again more too
by mbrumlow 9y ago
> and no amount of Ansible/SaltStack/Puppet script will save you from this.
And I am afrade you missed my point entirely if you are bring up yet again more tools and frameworks.
Owning your stack from the top to the bottom - with very few exceptions is what I am suggesting.
I too also speak from experience, and have a few years on you -- not that any of that matters.
If your environments diverged then you did not own your stack properly. It is within every engineers ability to build out a stack that runs the same on each environment. It just means understanding that problem domain and taking the time to write the code that fits.
Far too many times have I smacked the hand of a coworker suggesting using any of these bail wire and duct tape solutions you just mentioned. The end result is we have a wonderful system that we own and can ensure meets our needs. The same binaries, configurations and images are pushed from alpha to staging and finally production with full control of evey artifact at the start of the pipeline.
- gouggoug 9y agoI'm curious. Could you describe the kind of infrastructure you manage and the tools do you use? Are all your tools written in house? If so, what will happen when the author leaves the company?