Infrastructure as code: Difference between revisions

Revision as of 01:51, 7 September 2024

Latest revision as of 22:50, 18 August 2025

(8 intermediate revisions by 7 users not shown)

Line 4:

{{Technical|date=November 2021}}

}}

'''Infrastructure as code''' ('''IaC''') is the process of managing and provisioning computer [[data center]] [[Resource|resources]] through machine-readable definition files, rather than physical [[HardwareComputer random number generatorhardware|hardware]] configuration or interactive configuration tools.<ref name="AWS in Action, IaC" />

The [[IT infrastructure]] managed by this process comprises both physical equipment, such as [[bare-metal server]]s, as well as [[virtual machine]]s, and associated configuration resources.

The definitions may be in a [[Version Control System|version control system]], rather than maintaining the code through manual processes.

Line 56:

==Methods==

Infrastructure as Code (IaC) allows you to manage servers and their configurations using code. There are two methodsways ofto IaCsend these configurations to servers: the '[[push technology|push]]' and '[[pull technology|pull]]' methods. TheIn mainthe difference'push' ismethod, the mannersystem in whichcontrolling the serversconfiguration aredirectly toldsends howinstructions to bethe configuredserver. In the 'pull' method, the server toretrieves beits configuredown will pull its configurationinstructions from the controlling serversystem.<ref>{{cite Inweb the|last=Venezia push|first=Paul method,|date=21 theNovember controlling2013 server|title=Puppet pushesvs. theChef configurationvs. toAnsible the destination systemvs.<ref>{{cite webSalt | url=http://www.networkworld.com/article/2172097/virtualization/puppet-vs--chef-vs--ansible-vs--salt.html | title=Puppet vs. Chef vs. Ansible vs. Salt | last=Venezia | first=Paul | date=21 November 2013 | website=[[Network World]] | publisher=Network World | accessurl-datestatus=14 December 2015dead | archive-date=18 July 2018 | archive-url=https://web.archive.org/web/20180718030604/https://www.networkworld.com/article/2172097/virtualization/puppet-vs--chef-vs--ansible-vs--salt.html |archive-date=18 urlJuly 2018 |access-statusdate=dead14 December 2015 |website=[[Network World]] |publisher=Network World}}</ref>

==Tools==

Line 124:

| -

|-

![[Otter (software)|Otter]]

|[[Inedo]] (2015)

|Push

|Declarative and imperative

Line 136:

|Declarative and imperative

|[[Go (programming language)|Go]]

| -

|-

! [[OpenTofu]]

| [[Linux Foundation]] and contributors (2023)

| Push

| Declarative and imperative

| [[Go (programming language)|Go]]

| Terraform fork

|}

Line 154 ⟶ 161:

* [[Orchestration (computing)|Orchestration]]

* [[Continuous configuration automation]]

* [[Landing zone (software)]]

==References==