Infrastructure as code: Difference between revisions

Content deleted Content added
Add link
m Replaced citation needed with reference
Tag: Reverted
Line 6:
'''Infrastructure as code''' ('''IaC''') is the process of managing and provisioning computer [[data center]] resources through machine-readable definition files, rather than physical 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]].<ref>{{Cite web|date=2023-08-02|title=Infrastructure as Code|url=https://scanoncomputer.com/infrastructure-as-code-iac/|access-date=2020-03-02|website=scanoncomputer.com|language=en-us}}</ref>
The code in the definition files may use either scripts or declarative definitions, rather than maintaining the code through manual processes, but IaC more often employs [[declarative programming|declarative]] approaches.
 
Line 29:
 
==Advantages==
The value of IaC can be broken down into three measurable categories: cost, speed, and risk.<ref>{{cnCite web|date=September2023-07-07|title=Infrastructure 2019as Code|url=https://encyclopedia.pub/entry/33342|access-date=2020-02-04|website=encyclopedia.pub|language=en-us}}</ref> Cost reduction aims at helping not only the enterprise financially, but also in terms of people and effort, meaning that by removing the manual component, people are able to refocus their efforts on other enterprise tasks.{{citation needed|date=March 2017}} Infrastructure automation enables speed through faster execution when configuring your infrastructure and aims at providing visibility to help other teams across the enterprise work quickly and more efficiently. Automation removes the risk associated with human error, like manual misconfiguration; removing this can decrease downtime and increase reliability. These outcomes and attributes help the enterprise move towards implementing a culture of [[DevOps]], the combined working of [[Software development|development]] and [[Information technology operations|operations]].<ref >{{cite web
| url=http://devops.com/2015/05/14/moving-from-infrastructure-automation-to-true-devops/
| title= Moving from Infrastructure Automation to True DevOps