Re:DigitalOcean launches its container service
by mark-ruwt on Tuesday December 11, 2018 @06:13PM
(#18659878)
I started using this model in '15 and it's not fragile. At all. The less I'm relying on outside frameworks, the better I sleep at night.
Re:DigitalOcean launches its container service
by lotyrin on Tuesday December 11, 2018 @08:58PM
(#18660758)
Certainly understandable -- I'd prefer to keep things simple and just have some kind of validation in place rather than rely on an abstraction if I can get away with it.
Having maintained various automation over the course of the past decade and a half, I can say things do change around. Over the course of only a few years though, obviously you can stick to some LTS release of whatever you're using and be pretty confident that e.g. "some-package" does not get renamed to "some-package-version" or split into "some-core" and "some-utils", or have a package get upgraded to a version with some less-than-backward-compatible configuration options, etc.
Alternatively, pre-baking cloud images that have already run such a script and are ready to boot becomes pretty easy with a tool like Packer.
Though, as the underlying OS changes, you'll need something to validate your scripts' functionality against, and a tool that's a little more declarative might make them less fragile to those changes.