Difference between revisions of "Continuous configuration automation"
Jump to navigation
Jump to search
(Created page with "Continuous configuration automation is an approach to realize infrastructure as code (IaC) in the DevOps engineer...") |
|||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
[[wikipedia:Continuous configuration automation|Continuous configuration automation]] is an approach to realize [[infrastructure as code]] ([[IaC]]) in the [[DevOps]] engineering community. | [[wikipedia:Continuous configuration automation|Continuous configuration automation]] ([[CCA]]) is an approach to realize [[infrastructure as code]] ([[IaC]]) in the [[DevOps]] engineering community. | ||
=Notable [[CCA]] Implementations= | |||
The two camps have their popular implementations. For imperative [[IaC]], many uses [[Ansible]] as an example. For declarative [[IaC]],[[Terraform]] is often mentioned. | |||
Notable [[CCA]] tools include: | |||
{{:Table/CCA Tools}} |
Latest revision as of 07:22, 5 August 2021
Continuous configuration automation (CCA) is an approach to realize infrastructure as code (IaC) in the DevOps engineering community.
Notable CCA Implementations
The two camps have their popular implementations. For imperative IaC, many uses Ansible as an example. For declarative IaC,Terraform is often mentioned.
Notable CCA tools include:
Tool | Released by | Initial release | Method | Approach | Written in |
---|---|---|---|---|---|
Ansible | RedHat | 2012 | Push | Declarative and imperative | Python |
CFEngine | CFEngine | 1993 | Pull | Declarative | C[1] |
Chef | Chef | 2009 | Pull | Imperative | Ruby |
Otter | Inedo | - | Push | Declarative and imperative | - |
Pulumi | Pulumi | 2017 | Push | Declarative and imperative | TypeScript, Python, Go, C |
Puppet | Puppet | 2005 | Pull | Declarative | C++, Clojure since 4.0, Ruby |
SaltStack | SaltStack | 2011 | Push and Pull | Declarative and imperative | Python |
Terraform | HashiCorp | 2014 | Push | Declarative | Go |