3 ms·
I'd like to see a polished common configuration API. Currently, we have Chef, Puppet, Ansible, and Salt (amongst others) all working to create a sane common ab
by runlevel1 11y ago
I'd like to see a polished common configuration API.
Currently, we have Chef, Puppet, Ansible, and Salt (amongst others) all working to create a sane common abstraction on top of a rainbow of configuration files and command-line arguments.
Each of them have their strengths, and frankly they're all impressive in their own right. But there's only so much you can do to reign in the chaos of the bazaar.
The Docker workflow certainly has its merits. It's great for narrowing dev-prod parity and repeatability. I've embraced it, but I'm a bit anxious that we, as a community, might end up creating bigger black boxes -- Dockerfiles upon Dockerfiles.
- zdw 11y ago> I'd like to see a polished common configuration API. https://xkcd.com/927/ https://xkcd.com/927/
- atsaloli 11y agoWhat effort is this? URL please?
- mpdehaan2 11y agoHmm, I think your boxes can be still pretty transparent in that case - if anything more so, as you've got single-bash files versus perhaps directories and directories of content? In most organizations, all those Dockerfiles should be yours, and in source control. Relying on the blobs from others shouldn't be neccessary for most applications. Yes - in large organizations, a management problem probably does arise, but I think if you find copy/paste rising up you have to push that down into the base image, basically? I don't think a configuration API helps to be honest - what you would do is turn them all into a "greatest common divisor" type scenario, where as they feel different because they were trying to be different. I think you're best solved by organizationally mandating one of them within your company, as painful as that may be.