3 ms·
You say that they're not always declarative like it's a bad thing. Personally, I find it nice that we have the playbooks to build out our infrastructure and the
by btgeekboy 12y ago
You say that they're not always declarative like it's a bad thing. Personally, I find it nice that we have the playbooks to build out our infrastructure and the playbooks that perform a rolling upgrade of our application using the same syntax, variables, and inventories. If you keep your declarative playbooks separate from your procedural ones, you get more power than a declarative system alone can provide. (FWIW, we chose it not just for this, but because of its lack of an agent - we can use our configuration management to deploy software to customers' infrastructure without colliding with their own CM.)
Further, this (using a data language as a programming language) isn't without precedent. Both XSL and Ant have standard conditionals, loops, etc available for use.
- jimbokun 12y agoXSL and Ant are the poster children for why this is a bad idea.
- dj-wonk 12y ago> Both XSL and Ant have standard conditionals, loops, etc available for use. Yes, XSL and Ant got there first, but what fraction of us would like to see the same decision made again? :)
- vertex-four 12y agoSalt implements its declarative language as a separate thing (States) from its more imperative parts (Modules, Runners, and the like). That's probably a better abstraction.