Content deleted Content added
Line 111:
==Relationship to DevOps==
Infrastructure as Code can be a key attribute of enabling best practices in [[DevOps]] – Developers become more involved in defining configuration and Ops teams get involved earlier in the development process.<ref>{{cite web| url= http://info.easydynamics.com/blog/continuous-integration-infrastructure-as-code |title= Continuous Integration: Infrastructure as Code in DevOps | last= Ramos | first= Martin | website= easydynamics.com | date= 4 November 2015}}</ref> Tools that utilize IaC bring visibility to the state and configuration of servers and ultimately provide the visibility to users within the enterprise, aiming to bring teams together to maximize their efforts.<ref>{{cite report |title=Infrastructure As Code: Fueling the Fire for Faster Application Delivery |publisher=Forrester |date=March 2015}}</ref> Automation in general aims to takes the confusion and error-prone aspect of manual processes and make it more efficient, and productive. Allowing for better software and applications to be created with flexibility, less downtime, and an overall cost effective way for the company. IaC is intended to reduce the complexity that kills efficiency out of manual configuration. Automation and collaboration are considered central points in DevOps; Infrastructure automation tools are often included as components of a [[DevOps toolchain]].<ref>{{cite report | last= Wurster | first= Laurie F. |last2= Colville | first2= Ronni J. |last3= Height| first3= Cameron | last4= Tripathi | first4= Somendra | last5= Rastogi | first5= Aditi | title= Emerging Technology Analysis: DevOps a Culture Shift, Not a Technology| publisher= Gartner }}</ref>
==References==
| |||