DevOps Stack Exchange is a question and answer site for software engineers working on automated testing, continuous delivery, service integration and monitoring, and building SDLC infrastructure. It only takes a minute to sign up.
Sign up to join this community
I've heard about deployment pattern which sounds like "build one time, deploy multiple times".
If I manage the configuration via e.g. ansible templates or chef or any other CM tools, I don't have any pre-generated configuration. I have it generated on every deployment.
Why no tool follows this (logical) pattern for configuration? Does it worth at all?
Mostly because getting from an unknown state to a desired state is not a build step, at build you start from a known state, which is nil or blank, and create something.
But what you're missing, I think, is that with configuration as code you build the desired state once and deploy the resulting artifact multiple times.
For a Chef Cookbook as example, you would:
With that in mind, all tools built on the promise theory (ansible, chef, puppet, salt,...) do fulfill this pattern of build once and deploy multiple times.
